Manage Continuous Delivery Pipeline

Continuous Delivery Pipeline can now be toggled to show only Systems that are impacted by the selected Release.

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.

      System names are now 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 to open a panel with the System Details.
  7. View the version number of each System (if a version number exists).
  8. If Jenkins and Github integrations are enabled, version numbers are clickable:
    • If a version number is green, there is code ready to be built, and the Build Now button is ready to be clicked. Click a version number to open the Commit Build Release pop up for that System:
      If Github Integration Customization is not set up, the Build Now button will not be available.
    • The middle Build column shows the list of code check-ins and:

      • Their version number (a blank version number means that the build hasn’t taken place).
      • The number of commits, whether they passed or failed, and their version numbers for that System.
      • The File Changes. Number of:
        • Green: Additions.
        • Yellow: Changes.
        • Red: Deletions.
      • The Build Status (whether the build completed or failed).
      • And the date of the last build time.
    • The left-hand Commit column is blank until a build in the middle column is clicked.
    • The right-hand Release column is blank until a build in the middle column is clicked.
  9. Click the Ready to Build row.
  10. The Commit and Release columns populate:
    This pop up shows the full audit of all the builds.

    • Code commits for that build appear in the left-hand column.
    • JIRA, ServiceNow, or Plutora Test tickets associated with the build appear in the right-hand column.
  11. Click a Commit in the left-hand column:

    • Github opens and displays the actual code changes.
  12. Click a JIRA, ServiceNow, or Plutora Test ticket in the right-hand column to open that ticket.
  13. Click Build Now.

    The version number will populate once built. It will also be visible for the Component on the Environment pop up and in the TECR window on the linked Environment.


Set Up Continuous Delivery Pipeline

Enable Integrations (If Using)

Jenkins integration is no longer required in order to use Continuous Delivery Pipeline. Users can now manually select Summary Version checkboxes on Environments and choose what Version Numbers are displayed on Systems.

To set up Continuous Delivery Pipeline:

  1. Enable integrations, if using:
    1. Enable Jenkins:
      1. Follow the instructions in Jenkins Integration Customization. (These have been updated.)
    2. Enable Github:
      1. Follow the instructions in Github 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 booking.

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 blue-linked 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.
    Toggle Switch 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.
      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 Systems to the selected Environment Groups:

  1. Go to Environment > Groups or click Manage Groups on the Environment Map.
  2. Search for an Environment Group that has booked for the Release.
  3. Click an Environment Group (not the blue-linked Name).
  4. Click the Group Members tab.
  5. Search for the Environment that contains the System (if known).

  6. Click the System header to sort Environments by Systems and scroll down until you find the System.
  7. Drag and drop the Environment containing the System into the Group Members panel.
  8. Allow the Environment to use Jenkins (if using):
    1. Click the blue-linked Environment Name to open the Edit Environment pop up.
    2. Click the Release Automation tab on the Edit Environment pop up. 
    3. Follow sections 4-6 in the Setting Up Jenkins Integration article.
  9. Make the System’s version number appear in Continuous Delivery Pipeline View:
    1. Click the Details tab.
    2. Follow section 7 in the Setting Up Jenkins Integration article.
  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 June 4, 2020