About Turnovers

Turnovers are containers for steps and tasks used to deploy applications to an environment. Turnovers are created for release trains or application releases and deployed to environments reserved for the release train.

Each turnover is tied to a single environment, but turnovers created from release trains can contain multiple application releases. Turnovers created from an application release are specific to that release.

Turnovers that are successfully deployed can be promoted to a different environment.

Turnovers follow a process organized into these phases:

Definition

Participants:

Developers
Release Engineers

Typically, developers create turnovers form application releases. Depending on their privileges, they can also do so from a release train. Regardless of where the turnover is created, it must be associated with an environment.

Turnovers can be created at these points in the release process:

For release trains, turnovers can be created from the construction, verification, or deployment stages of the process.
For application releases, turnovers can be created when the release is in the Executing or Closed workflow states.

Once a turnover is created, developers or release engineers can:

Schedule deployment. You can see if your target environment has any scheduling conflicts. If so, you can modify your schedule or choose a different environment, if one is available.
Add deployment tasks. These can be newly created tasks specific to the turnover or copied from runbooks and other turnovers. Deployment tasks can be added, reordered, or deleted until a turnover is deployed. For details, refer to The Task Collection Widget.
View and associate development tasks from the application releases associated with the turnover. These tasks are considered to be complete and can be viewed by clicking the Show Delivered link on the Requirements/Development tab for a release train or application release.

Once the turnover is defined, it is sent to a release engineer for acceptance. Once accepted, the turnover moves to the delivery phase.

Delivery

Participants:

Release Engineers

Accepted turnovers move to the "Ready to Deploy" state until their scheduled deployment date.

Once a release engineer starts the deployment, deployment tasks are automatically created in either the Manual Deployment Tasks process app or in Release Automation. Manual tasks must be completed by the task owner; automated tasks are completed in Release Automation.

Once all tasks are complete, the turnover moves to the Deployed state. If any manual or automated tasks fail, the turnover is sent to the Deployment Failed state. Failed turnovers can be retried or returned to development for more work. Previously successful steps can be re-executed or skipped during a turnover "retry."

Successful deployments are then closed.

The Task Collection Widget

The Task Collection widget is available on all turnovers. To open the widget, click the Deployment Tasks tab for a turnover.

To add, copy, modify, or delete deployment tasks, click Edit Deployment Tasks in the upper right corner. Use the links in the upper right corner of the widget to modify the list of deployment tasks.

Once you have a task list, use one of these methods to change their deployment sequence:

Click the sequence column header to reorder the entire list.
Double-click inside a row in the sequence column reorder individual tasks in the list.

For information on the deployment hub that populates the selections for deployment tasks, see Deployment Task Integration.