Deploying Release Packages

After you have scheduled the deployment, you are ready to run the deployment. This initiates the processes that you have already configured and scheduled.

Prerequisites: You must have completed the release package configuration, including adding the deployment tasks.

Starting the Deployment

To run a release package deployment:

Select the release package you want to deploy.
Move the release package through its lifecycle until the Start Deploy option is available.
Click Start Deploy and enter any comments needed in the Message Log field.
The deployment is initiated and the deployment tasks associated with the release packages begin.
Check the deployment status.
After the deployment has been verified, click Deployment Verified and enter any comments needed in the Message Log field.
After testing is complete, click Complete Testing or Failed Testing and fill out the resulting form as needed.

Note: Even if you have a schedule and the start date has not yet arrived, when you click Start Deploy, the deployment starts; the schedule is not enforced by the software, and is for informational purposes.

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.

Checking Deployment Status

To check the status of the deployment:

Select the release package's Deployment Tasks tab.
Filter the list of deployment tasks by task executions.
Refresh the status as needed using the refresh button.
The status of the deployment task may differ depending on the plugin implementation. Typically:
- Deployment tasks requiring manual action stay in the Active status until the open item is completed.
- Deployment tasks that initiate external processes show the status as the process for the task is executed and information is retrieved from the product to which the Provider plugin integrates.

If the deployment fails, you should investigate and fix whatever caused the problem, such as the configuration in the integrating product, a selection or sequencing problem in the deployment tasks, or configuration in the target environment itself. If the environment allows redeployment, you can redeploy the release package to the same environment. If it doesn't allow redeployment, you must return the release package to construction and progress the release package back through the process from there.

Deploying to the Next Environment

Use the provided options to transition the release package through the deployment process. When the deployment is marked complete for an environment, a list appears with the available environments for the next deployment. You will see the upcoming optional and required environments listed, and you can select the one to which you want to deploy, skipping the optional ones if desired. Start the deployment in the next environment and continue until you have completed the deployment to the last environment in the deployment path.

When the deployment is completed in the last environment of the deployment path, a message appears telling you that the release package has been promoted to all environments and the release package is now complete.

Viewing the Deployment Executions for the Path

The deployment information about each environment in the deployment path for which you have run a deployment is shown in a tabular report below the deployment path.

If you do not see the complete report below the deployment path and the environments to which you have deployed are not shown in color, refer to Troubleshooting the Deployment Log.