Project Settings

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

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

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 Security module.
Whether or not you can delete a project depends on the authorizations you have for it.

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 and description. Its application level is also indicated with 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.

Click the environment variable to view its information. A panel opens. You can edit its information from this panel.

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

Environment variable can be defined as passwords. Select the option is password if your value is a password and must be hidden.

Environment variables are unique within a scope, but an inferior level can override a higher level. For more information, see Overriding Environment Variables.

To access this page click Projects All Projects My Project Environment Variables.

Environment variables can be created at the platform, project, pipeline, and app level, allowing you to have values dedicated to a specific scope without impacting the others. Therefore, you will find an Environment Variables page for each scope.

At the platform level: At this level, the Environment Variables page allows you to access 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 Environment Variables page gives you access to the environment variables defined for the selected pipeline. For more information, see the Environment Variables page of a pipeline.
Within an app: At this level, the Environment Variables page gives you access to the environment variables defined for the selected app. For more information, see the Environment Variables page of an app.

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.