Continuous Delivery Pipeline


Continuous Delivery Pipeline displays the Environment Groups that have been booked for a selected Release and allows users to track Systems and their version numbers within each Environment Group from development to production.

For example: If a company’s Development, Testing, UAT, Preproduction, and Production areas each had an Environment Group, users could use the Continuous Delivery Pipeline to track what version of each System was being used by each Environment Group and whether the Environment Group even contains the correct Systems.

You can add and edit Environment Groups on this page and set what Systems appear on the Continuous Delivery Pipeline page.

When testers or product owners deploy new features at scale, the Continuous Delivery Pipeline allows them to:

  • See at a glance what version of the new feature can be found across their Environment Groups.
  • Get visibility back into source code change history and build/deploy history.
  • Perform self-service builds to Test Environments, invoking builds from the UI as a part of Continuous Delivery.

You cannot edit Systems and Environment Groups from here.


You must have the ‘View Continuous Delivery Pipeline’ user permission.

Environment > Continuous Delivery Pipeline

Access Continuous Delivery Pipeline

Navigate to Environment > Continuous Delivery Pipeline and select a Release/Project from the drop-down. 

View Options

Environment Group

The columns represent each Environment Group that has been booked for the Release. The order left to right is based on the end date of the bookings. SIT Environments are booked earlier than UAT, for example, so they are to the left of UAT Environment.


Rows represent the appearance of a System associated with that Environment Group. If Builds are toggled off, the Environment Component’s Summary Version number is displayed, and if Builds are toggled on Build Tag and Build # is displayed. See Manage Builds.

System Details

Click a System version number to open a panel with the System Details, including the ‘Builds’ field, if Builds are enabled. See Manage Builds.

Impacted Systems

Click the Only Show Impacted Systems toggle switch. Impacted Systems are those that have been dragged and dropped into the:

  • Impacted Systems panel under the Systems tab of the selected Enterprise, Project, or Independent Release.
  • Regression Systems panel under the Systems tab of the selected Project or Independent Release.

Impacted Systems have version numbers that will increment for the selected Release.

Full Screen

View Continuous Delivery Pipeline in full screen, Click . Then click Full Screen. To exit full-screen mode, press the Escape key on your keyboard.

Manage Continuous Delivery Pipeline

Enable Integrations (If Using)

To set up the Continuous Delivery Pipeline you need to enable Jenkins. Follow the instructions in Jenkins Integration Customization.

Add Environment Groups to a Release

Environment Groups appear as a row of columns in the Continuous Delivery Pipeline, ordered by the end date of their bookings.

To add Environment Groups to a Release:

  1. Go to Release > Manager.
  2. Click the Releases to display the existing Releases on the grid.
  3. Open a Release by clicking on the Release ID or Release Name.
  4. Click the Environments tab.
  5. Search for the Environment Group.
  6. Drag and drop the Environment Group into the Phase.
  7. Click .

Change the color of the Environment Group header row color

  1. Go to Environment > Groups or click Manage Groups on the Environment Map.
  2. Search for Environment Groups.
  3. Double click the Color column and select a color from the drop-down menu or type a Hex value and press the Enter key on your keyboard to set the Hex value. For details, see Edit the Environment Group Color.

Add and Manage Systems in the Environment Groups

Systems appear as rows in each Environment Group column.

Add the selected Environment Groups’s Environments to Systems:

  1. Go to Environment > Groups or click Manage Groups on the Environment Map.
  2. Search for an Environment Group that has been booked for the Release.
  3. Click an Environment Group row (not the Name).
  4. Click the Group Members tab.
  5. Click an Environment Name under the Group Members panel to open that Environment.
  6. Select a System for that Environment.
  7. Click .
  8. Follow the Setting Up Jenkins Integration article to add Jenkins jobs to that System.
  9. Enable Builds entity to see Build Tags and Build Number appear as the version numbers instead of the Environment Component’s Summary Version. See Manage Builds.
  10. Refresh Continuous Deployment Pipelines in your browser to see your changes.

Related Articles


Be the first to find out about new features. Subscribe to the Release Notes email.

Was this article helpful?

Thanks for your answer!