Starting Deployment

Deployment of deployable release trains or parent or standalone release packages initiates the deployment tasks that you have configured and scheduled.

Prerequisites: You must have completed the configuration for deployment tasks.

It is recommended that you validate the deployment tasks before beginning the deployment. See Validating Deployment Tasks.

To run a deployment:

  1. Select the deployable release train or release package you want to deploy.
    Note: Standalone and parent release packages can be deployed directly. Child packages are deployed when their parent release package is deployed.
  2. Move the item through its lifecycle until the Start Deploy option is available.
  3. Click Start Deploy and enter any comments needed in the Message Log field.

    The deployment is initiated and execution of associated deployment tasks is initiated. After any scheduling criteria is met for deployment tasks and any required approvals are made, the deployment executes each of the deployment tasks in the order specified.

    Important: When you initiate deployment into environments that require approval, approvals will be successfully generated only if you have the RLC - Approvers role. If deployment dates are required, specify them in the environment schedule, see Scheduling into Environments. For environments with approvals, the Start Deploy button is displayed only if deployment dates are specified (even if they are not required in a rule).

    After you click Start Deploy, validation automatically begins. If the deployment tasks are valid, deployment starts immediately. However, if any task is invalid, deployment will not start. The release package will remain in the Ready to Deploy state and the following message will appear:

    "The current or locked environment has invalid tasks. See the System Log for more information."

  4. Check the deployment status.
  5. After the deployment has been verified, click Deployment Verified and enter any comments needed in the Message Log field.
  6. After testing is complete, click Complete Testing or Failed Testing and fill out the resulting form as needed.
Labels and options on the page typically direct you on what to do as you navigate through the deployment.
Important: You cannot add environments or change the options once the release package is started on the deployment path. To add environments and change the options, you must change the deployment path and start again.

Related Topics

A Typical Release Control Flow Using Deployable Release Trains

A Typical Flow Using Release Packages Only