Creating Release Packages

You should create a release package when you are ready to begin configuring the deployment details for a release. You can create release packages by submitting to the release packages project. If using release trains, you can create a release package directly from a release train.

By default release packages are standalone, but they can be designated as parent or child packages. See Designating Release Packages as Parents and Linking Release Packages.


To create a release package:

  1. Depending on whether you are using release trains, open the release packages project submit form in one of the following ways:
    • In Work Center, select a release train, and in its Overview tab, click Create Release Package.

    • In Work Center, click +New and select your release packages project.

      (By default, the Release Packages project is used to store release packages.)

  2. Fill out the required fields.
    Tip: Include the version of the release package in the Title or Description so that you can later report on and compare release package versions through standard SBM reports.
  3. Fill out optional fields as needed.
    • Use task templates to save time and enable reuse of deployment tasks. In the Overview section, in the Use Task Template field, select a task template from which to copy deployment tasks.
    • Under Options:
      • Select custom column items for add and display of deployment units and requests. See Custom Columns.
      • Select whether to require that failure tasks be run if the deployment fails in an environment. See Adding Failure Tasks.
      • Select plugin configuration fields for which the values can be overridden for this release package. See "Overriding Configuration Settings" in the plugins documentation.
      • Select task action rules to restrict the set of rules that apply for this release package. If none are selected, all defined task action rules apply. See "Task Action Rules" in the plugins documentation.
      • Select whether or not to bypass the Deployed state. By default, the release package process flow bypasses this state. If you want to have users manually transition to this state, you can set the option to No.
  4. Click Submit.

    This places the release package in the Acceptance state.

    Note: You can instead click Save as Draft, which places the release package in the Construction state, where it must be configured before delivering it to the release engineering team for acceptance.
  5. Configure and manage the release package using the tabs that appear in the form.

Required Fields

The required fields when you create a release package are as follows:


The tabs available from a release package once it is created are as follows:

Updating Release Packages

Once created, you can update release packages as follows:

  1. In the Release Control application group left navigation, expand the Release Packages section and select one of the activities sections to display the desired list of release packages.
  2. Select a release package and click the Update button to edit it.

Options available depend on the process app workflow. For details on the default workflow, see About the Release Train Process App.

Related Topics

About the Release Package Process App

About the Deployment Path Application

About the Approvals Process App

Creating Deployment Paths

Adding Deployment Units

Adding Deployment Tasks

Creating Task Templates

Adding Requests