As part of the deployment task planning, you can associate deployment tasks to release package stages by creating them as part of the release package associations, or you can create them as part of deployment process templates and then apply them to release package stages.
The specification of the deployment tasks is the same whether you create them in a release package or in a deployment process template view.
You can specify manual, approval, vault, and automation tasks that will be executed upon deployment of your release package to a specific stage.
Tasks can be assigned sequence numbers to control the order of execution. The sequence numbers are handled as follows:
By default the sequence number is set to 0. If you do not overtype the sequence number, the task is initiated immediately after the deployment of the release package to the stage with which the task is associated.
Sequentially ordered tasks are executed in order.
Tasks with the same sequence number are executed in parallel. For example, if several tasks have sequence number 3, all of those tasks are initiated when all tasks with sequence number 2 are complete.
Deployment task planning includes the following: