Manage Continuous Delivery Pipeline

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

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

To set up Continuous Delivery Pipeline:

  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.
  3. Add Environment Groups to a Release:
    1. Go to Release > Manager.
    2. Edit a Release by clicking on the blue-linked Release ID or Release Name.
    3. Click the Environments tab.
    4. Search for the Environment Group.
    5. Click a Phase toggle switch until it is blue and On.
      Toggle Switch On
    6. Drag and drop the Environment Group into the Phase.
    7. Click Save and Close.
  4. Change the color of the Environment Group header row color:Continuous Delivery Pipeline Oct 17 2017 header row
    1. Go to Environment > Groups or click Manage Groups on the Environment Map.
    2. Search for Environment Groups.
      Environment Group display color search
    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.
        Environment Group display
      3. Press the Enter key on your keyboard to set the Hex value.
  5. Add Systems to the Environment Group:
    1. Go to Environment > Groups or click Manage Groups on the Environment Map.
    2. Search for the Environment Group.
      Environment Group display color search
    3. Click Details.
      Environment Group display color details
    4. Click the Group Members tab.
      Manage environment groups Group members tab
    5. Search for the Environment that contains the System (if known).
      Sort by systems Environment Groups search
    6. Click the System header to sort Environments by Systems and scroll down until you find the System.
      Sort by systems Environment Groups
    7. Drag and drop the Environment containing the System into the Group Members panel.
      Manage environment groups drag and drop
    8. Allow the Environment to use Jenkins:
      1. Click the blue-linked Environment Name to open the Edit Environment pop up.
        Manage environment groups name
      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.
  6. View Continuous Delivery Pipeline in full screen:
    1. Click More Tools.
      Continuous Delivery Pipeline Oct 17 2017 mroe tools
    2. Click Full Screen.
    3. Press the Escape key on your keyboard to exit Full Screen mode.

The Continuous Delivery Pipeline page 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.

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 left to right order is based on the end date of the booking.
    • Rows representing the appearance of a System associated with that Environment Group.
    • Click a System to open a panel with the System Details.
    • The version number of each System (if a version number exists).
    • If a version number is green, there is code ready to be built, and the Build Now button is ready to be clicked.
      If Github Integration Customization is not set up, the Build Now button will not be available.
  4. Click a version number (above) to open the Commit Build Release pop up for that System:

    • The middle Build column shows the list of code check-ins and:
      • Their version number ( a blank version number means 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.
  5. Click the Ready to Build row.
  6. 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.
  7. Click a Commit in the left-hand column:

    • Github opens and displays the actual code changes.
  8. Click a ticket in the right-hand column to open that ticket.
  9. Click Build Now.

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


Back to the top arrow

Was this article helpful?

1 found this helpful.