About Deployment

To deploy an application release, each turnover for that application release must be deployed to each environment in its deployment path.

Deployment for each turnover is scheduled through the turnover lifecycle. The default options of a turnover leading up to deployment are as follows:

Deliver, Accept, Start Deploy

When you click Start Deploy in the turnover, this initiates a series of events as follows:

The deployment tasks associated with the turnover and current environment in the deployment path are initiated in the given order.
- Automation deployment tasks initiate the Release Automation processes for the component versions selected.
- Manual deployment tasks submit task items into the designated SBM process app, where the owner must complete the work and complete the manual task.
If the deployment fails, you can fix any issues and then use the Retry option to initiate the sequence of deployment tasks again in the same environment. You also have the Fail option in case you want to cancel the deployment to this environment for some reason.
If the deployment is successful, the turnover enters the Deployed state where QA can verify the deployment.

Component versions are deployed using automation deployment tasks. The application process and component versions selected in a deployment task initiate the component processes associated with the component versions in Release Automation.

Review the deployment results as follows:

Select the turnover Deployment Tasks tab to view the list of tasks by environment or selected deployment. Filter by deployment to see specific error or informational messages for each task for that deployment.
Select the turnover Deployment Path tab to view the history in context of the deployment path. Below the deployment path is the history of deployment, with what happened on each deployment run.

Related Topics

Scheduling Deployment

About Turnovers

Configuring and Deploying Turnovers