Manage Builds in System

Introduction

You add or edit Builds to the System in the ‘Recent Builds’ section in the Systems pop-up. This article provides a brief overview of the steps to add/edit Builds to the Systems manually and via automated jobs. See Builds for more information.

Pre-requisite

You must have the following user permissions:

  • Create Builds
  • Edit Builds
  • Delete Builds

Ensure that Enable Builds is selected in Build Setup.

Environment > Systems

Access ‘Recent Builds’ section 

To access the Recent Builds section:

  1. Navigate to the ‘Systems’ page.
  2. Search for the System in which you want to add/edit the Builds. You can use the filter options available on this page.
  3. Open the System by clicking on the System Name.

The Systems pop-up displays. Scroll down to the ‘Recent Builds’ section. The existing Builds that are added to the System, if any, are displayed here.

Add a Build Manually

Builds created manually have fewer fields and can be added via Systems or via the Builds grid.

To add a Build click . ‘Add New Build’ pop up displays:

  1. System is grayed out, with the current System selected.
  2. Select a Linked Release:
    • Linked Releases available for selection are:
      • Active. In other words, not Completed or in an end state.
      • Linked to the selected System.
      • If a parent Enterprise Release is selected, the child Releases will also be displayed.
      • If a child Release is selected, the parent Release will not be displayed.
  3. Select a Linked Change:
    • Linked Changes available for selection are:
      • Linked to the selected System.
      • If a Linked Release is selected above, only Changes linked to the System and the Release can be selected.
  4. Select an Environment:
    • Environments available for selection are:
      • Linked to the System.
  5. Click the Manual tab if it is not already selected.
  6. Type a Build #. (Mandatory.) (Usually, the internal version number.)
  7. Type a Build Tag. (Usually, the external version number, such as 3.1.1.)
  8. Type a Branch. (Usually, the name of the branch from the source control management tool.)
  9. Select a Build Status. (Mandatory.)
  10. Click .

The new Build displays in the ‘Recent Builds’ section.

Add Build using Automated Jobs

To add Jenkins jobs to Builds from a System:

Click . ‘Add New Build’ pop up displays:

  1. System is grayed out, with the current System selected.
  2. Select a Linked Release:
    • Linked Releases available for selection are:
      • Active. In other words, not Completed or in an end state.
      • Linked to the selected System.
      • If a parent Enterprise Release is selected, the child Releases will also be displayed.
      • If a child Release is selected, the parent Release will not be displayed.
  3. Select a Linked Change:
    • Linked Changes available for selection are:
      • Linked to the selected System.
      • If a Linked Release is selected above, only Changes linked to the System and the Release can be selected.
  4. Select an Environment: The Environments linked to the System will be available for selection.
  5. Click the Automated tab if it is not already selected.
  6. Click to select the checkboxes of Automated Jobs (sourced from Jenkins or Integration Hub).
  7. Select Parameters:
    1. Click + Parameters and select or type the parameters. If default parameters were set, their values can be edited at this point but new parameters cannot be added.
    2. Click Save & Close.
  8. Click .

The new Build displays in the ‘Recent Builds’ section. 

Click on the Systems pop-up.

View Build Details

The ‘Recent Builds’ section loads the 25 most recent Builds for the System. The Build Status updates in real-time when a Build is run. 

To see all the Builds for this System, go to Environment > Builds and filter by System. 

Edit Builds

To edit Builds, click Build # to open the ‘Builds’ pop-up and update the Build details as required. For more information, see Add/Edit Builds.

Related Articles

Contents

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

Was this article helpful?

Thanks for your answer!