When you schedule a deployment, you select the release, the release environment, associated application versions, and the deployment plan. Beginning at the scheduled start time, you and your team resolve the deployment's tasks (defined in its deployment plan). Deployments can start automatically at the scheduled time or manually. Rules can also be defined to run deployments on a recurring schedule. When a deployment starts, regularly updated feedback provides information about the deployment's progress. You can also modify existing tasks and add new ones even after the deployment starts. When all tasks are resolved, the deployment is complete.
Deployment plans define a deployment's segments and tasks. Typically, you create deployment plans from existing plans but you can start with a blank plan. When you create a deployment plan, regardless of whether it is based on an existing plan, you associate it with a release. Each release-plan combination is unique. You can add or delete segments and tasks even after a deployment starts. Changes that you make to a plan during a deployment become part of the plan itself. You can also work on a deployment plan directly outside of any deployment.