Manage Continuous Delivery Pipeline

When testers or product owners deploy new features at scale, 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.

Introduction to 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 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.

Systems and Environment Groups cannot be edited from Continuous Delivery Pipeline.

To view the features of Continuous Delivery Pipeline:

  1. Go to Environment > Continuous Delivery Pipeline.
  2. Click to select a Release/Project.
  3. The following items display:
    • Columns representing each Environment Group that has been booked for the Release:

      • The order left to right is based on the end date of the bookings. Development Environments are booked earlier than UAT, for example, so they are to the left of UTA Environments.
    • Rows representing the appearance of a System associated with that Environment Group:

      • The gray version numbers are the Environment Component’s Summary Version number if Builds are toggled off, and Build Tag and Build # if Builds are toggled on. See Manage Builds.
      • System names are displayed in black above their Environment’s names to make it easier to track System updates across your Environments.
  4. Click the Only Show Impacted Systems toggle switch:

    • Impacted Systems are those that have been dragged and dropped into the:
    • Impacted Systems have version numbers that will increment for the selected Release.
  5. View Continuous Delivery Pipeline in full screen:
    1. Click More Tools.
    2. Click Full Screen.
    3. Press the Escape key on your keyboard to exit full-screen mode
  6. Click a System version number to open a panel with the System Details, including the Builds field, if Builds are enabled. See Manage Builds.

 

Manage Continuous Delivery Pipeline

Enable Integrations (If Using)

To set up the Continuous Delivery Pipeline:

  1. Enable Jenkins, if using:
    1. Follow the instructions in Jenkins Integration Customization.

Add Environment Groups to a Release

Environment Groups appear as a row of columns in 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 toggle button (if present).
  3. Edit a Release by clicking on the Release ID or Release Name.
  4. Click the Environments tab.
  5. Search for the Environment Group.
  6. Click a Phase toggle switch until it is blue and On.
  7. Drag and drop the Environment Group into the Phase.
  8. Click Save and Close.
  9. 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. Manage Environment Group colors:
      1. Double click the Color column and select a color from the drop-down menu.
        Or:
      2. Type a Hex value.
      3. Press the Enter key on your keyboard to set the Hex value.

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. Click to select a System for that Environment.
  7. Click Save & Close.
  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.

 

Back to the top arrow

Be the first to find out about new features. Subscribe to the Release Notes email. Subscribe Now
Updated on October 6, 2021

Was this article helpful?