Project Settings

This topic presents the setting options available for your project, which include the Icon for environment variables Environment Variables, Icon for Docker credentials Docker Credentials, and Icon for external connections External Connections pages.

Project Settings

Project settings are accessible by clicking The settings icon is a gear. Project settings from any page that appears in the secondary navigation menu after selecting a project from the The "All Projects" page icon is a folder and the same as the "Projects" module. Projects module library.

It includes the following non-versioned and editable features:

1. Name

Names are mandatory. They can be up to 255 characters long and must be unique within a project.

2. Description

Descriptions are optional and not restricted. However, it is a good practice to add them. Keep them short and to the point.

3. Job Technologies

It includes embedded and external job technologies, which can be specified for the selected project.

If a technology is used by a job in your project, you cannot remove it from the technologies available in the project. On the other hand, if a technology is not selected in the project settings, it will not be available, and you will not be able to use it in the project.

For more information about jobs, see About Jobs.

4. App Technologies

App technologies can be specified for the selected project.

If an app is used in your project, it cannot be removed from the technologies available in the project. On the other hand, if a technology is not selected in the project settings, it will not be available, and you will not be able to use it in the project.

For more information about apps, see About Apps

Click the information icon info circle to view a description and the available contexts of a technology.

Screenshot of the technology details panel that appears when you click on the "i" of the information icon
The job and app technologies available to choose for your projects are determined by the Technology Catalog.

5. Authorizations

Groups can be added with a role to access only the selected project:

Table 1. Access Role Table
Roles Description

Viewer

Has read access to the project.

Editor

Has read and edit access (example: edit jobs) to the project.

Manager

Has read and edit access (example: edit jobs) to the project, can delete it and modify its settings and configuration (example: run type, versions).

  • You can specify access rights for groups of users only.

  • Some groups have access to all projects of the platform. You can manage those rights in the The "Security" module icon is a shield with a person icon inside. Security module.

At the bottom of the primary navigation panel is a delete Delete project button. You may or may not be able to delete a project depending on your authorizations for that project.

Environment Variables Page

This Icon for environment variables Environment Variables page gives you access to the project’s environment variables.

Environment variables are listed with some basic information, such as the name, description, and application level, indicated by the Project badge envvar project label.

At the project level, the Icon for environment variables Environment Variables page gives you access to the environment variables defined for the selected project but also to the global environment variables. However, you can only create and edit environment variables for the project.

You can create up to 200 environment variables per project. Once you reach this limit, the create button becomes unavailable, preventing you from creating new environment variables.

To view the information of an environment variable, click it. A panel opens with the information that you can also edit.

You can define your environment variable as a password. Select the option is password if your value is a password and must be hidden.

When viewing the details of a global environment variable in a project, you can choose to override it for that project only by clicking Override in this project. The global environment variable will still exist at the platform level and will still apply in other projects. For more information, see Overriding Environment Variables.

To access this page click The Projects module icon is a folder. Projects  The Projects module icon is a folder. All Projects  My Project  Icon for environment variables Environment Variables.

Environment variables can be created at the platform, project, and pipeline level, allowing you to have values dedicated to a specific scope without impacting other projects or pipelines. Therefore, you will find two other Environment Variables pages.

  • At the platform level: At this level, the The "Environment variables" module icon is a rectangle with the "VAR" written in it. Environment Variables page allows you to access, create, and edit only the global environment variables, that is, environment variables defined for all projects on the platform.
    For more information, see the Environment Variables page of a platform.

  • Within a pipeline: At this level, the The "Environment variables" module icon is a rectangle with the "VAR" written in it. Environment Variables page gives you access to the environment variables defined for the selected pipeline but also to the project and global environment variables. However, you can only create and edit environment variables for the pipeline.
    For more information, see the Environment Variables page of a pipeline.

External Connections Page

The External Connections External Connections page gives you access to the project’s external connections and enables you to manage them.

What is an external connection?

An external connection is a connection parameter specific to an external technology provider, used when creating external jobs in projects. It includes at least the remote host information and authentication requirements used to connect to the external job technology.

External connections are listed with some basic information, such as the name, connection type, related jobs, and creation date.

You can create new external connections by clicking Add connection and fill in the required information.

To view more information about an external connection, click it. A panel opens with the information that you can also edit.

Docker Credentials Page

Some types of jobs and apps use Docker images. When a Docker image is private, Docker credentials must be provided for your Saagie platform to access the image.

What are Docker credentials?

Docker credentials are login information stored in projects to allow you to pull Docker images from private registries when creating apps.

Docker images are project specific and can only be used in the project they are added to. The same Docker credentials can be added to multiple projects.

Docker credentials are listed with little information, such as the credential type, name, and date the credentials were added. Click a credential to view more details, such as the credential type, your username and password, the connection status, whether your credentials are used or not, and the date they were added to your project.

If your credentials have been used, a searchable list of jobs and apps that use them is displayed.

  • If your Docker credentials are used, deleting them may cause problems for jobs or apps that use them.

  • Saagie does not receive any type of image list type accessible with your Docker credentials.