About Pipelines

By default, the page opens when you click a pipeline in the project’s pipeline library.

The first part of the page (1) provides general information about the pipeline, such as the name and description, and other pipeline settings.

The second part of the page (2) provides information about the pipeline instance such as the last status, the start and end date of the last instance and its duration, whether the pipeline variables were editable at runtime, the version used, and the pipeline creator.
In addition, you can see the progress of a running pipeline in real time. When a pipeline is running, you can select a job to see its overview. When a job has finished running, you can view its execution logs, and the summary table of used and modified variables (4), if the setting for modifying variables at pipeline execution was enabled.

The third part of the page (3) provides information about the pipeline consumption through different graphic resources. Use these graphs to check your pipeline consumption during its execution.

The fourth part of the page (4) provides information about the used and modified variables. It is displayed if you select See variables from the context menu of a job or en environment variable condition. The setting for modifying variables at pipeline execution must be enabled to access this table.

Whenever you run a pipeline, a new instance of that pipeline is created. All instances are saved and remain accessible: they are listed on the right side of the page (1). You can view the information of an instance by selecting it in the list.

By default, the page opens on the last executed instance of the selected pipeline.

The first part of the page (2) provides general information about the instance of the pipeline, such as the instance number (specified by #001 in the title), its execution status, the version of the pipeline used, the start and end times and duration, and whether the pipeline variables were editable at runtime.

The second part of the page (3) allows you to see the progress of the pipeline orchestration for the selected instance.
In addition, you can see the progress of a running pipeline in real time. When a pipeline is running, you can select a job to see its overview. When a job has finished running, you can also view its execution logs, and the summary table of used and modified variables (5), if the setting for modifying variables at pipeline execution was enabled.

The third part of the page (3) provides information about consumption of the selected pipeline instance through different graphic resources. Use these graphs to check your pipeline consumption during its execution.

The fourth part of the page (4) provides information about the used and modified variables. It is displayed if you select See variables from the context menu of a job or en environment variable condition. The setting for modifying variables at pipeline execution must be enabled to access this table.

To edit the pipeline, click Upgrade pipeline (5). It allows you to modify the name and description, the settings, add and delete jobs and conditions. Upgrading your pipeline creates a new version of it.

Whenever you upgrade a pipeline (1), a new version of that pipeline is created and automatically defined as the Current version.
All versions are saved and remain accessible: they are listed on the right side of the page (2). You can view the information of a version by selecting it in the list.
You can switch back and forth between versions as required by selecting a version from the list and clicking Rollback to this version (3). This action of rolling back to another version of the pipeline will make the selected version the new Current version.

By default, the page opens on the version of the pipeline in use, tagged with the Current badge.

The first part of the page (5) provides general information about the version, such as the version number, the release note, and the creation date and creator.

The second part of the page (6) displays the pipeline version orchestration.

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

At the pipeline level, the 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.

You can create up to 200 environment variables per pipeline. 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 or project environment variable in a pipeline, you can choose to override it for that pipeline only by clicking Override in this pipeline. The global or project environment variable will still exist at the platform or project level and will still be applied, except in this pipeline. For more information, see Overriding Environment Variables.

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