About Runbooks

Runbooks are templates for a collection of ordered deployment tasks. These tasks can be manual steps in the process or automated tasks that are executed in Release Automation.

Runbooks can be created directly from the Runbooks application or from turnovers. Deployment tasks from approved runbooks can be copied to turnovers.

Note: Component versions and snapshots cannot be associated with runbooks. These are associated only with turnovers, which are for specific deployments.

Participants:

Release engineers
Release manager

Runbooks follow a process organized into these phases:

Create
Release engineers typically create a runbook and add deployment tasks. Tasks can be also copied from other runbooks or turnovers.

Once tasks are added, the runbook is sent to a release manager for review.

For details on task creation, refer to About Deployment Tasks.
Active
Once a runbook is accepted, tasks can no longer be added or modified.

The runbook's tasks can be copied to turnovers, however, and reordered and modified as needed. New deployment tasks can also be added to turnovers.

Note: To modify an accepted runbook, return it to the construction state.
Inactive
Inactive runbooks are no longer available to turnovers.

Related Topics

Creating Runbooks