About Deployment Tasks

Deployment tasks include the details of what is to be deployed, what order they are to be deployed in, and what needs to be done before, during, and after they are deployed. Sets of deployment tasks can be saved to runbooks that can then be applied to other turnovers.

Creating Deployment Tasks

When you create a deployment task, you select the type, manual or automation.

• Manual deployment tasks are used to submit items into SBM projects that your personnel use to assign and track their work. You may use the provided Manual Deployment Task process app or use other process apps for this purpose. When manual deployment tasks are run, items are submitted into the designated SBM project at the designated transition and assigned to an owner. When the item is closed by the owner, the manual task is also considered complete.
• Automated deployment tasks are used to initiate Release Automation processes. When the deployment tasks are run, the designated component versions or snapshots are automatically configured and deployed into the designated environments.

Initiating Deployment Tasks Through Turnovers

1. When a turnover is deployed, deployment tasks are initiated in the order specified in the sequence. As a deployment task is completed, the next task in the sequence is initiated and completed. This process occurs until all deployment tasks are complete.
2. Manual deployment tasks are submitted into the SBM project specified for the task and assigned to an owner; automated tasks are created and completed in Release Automation.
3. After all deployment tasks are successfully completed, the turnover is automatically sent to the Deployed state. If any tasks fail, the deployment fails.