Running deployments#

Complete deployments by resolving the tasks in a deployment plan.

A deployment starts when one of the plan's eligible tasks starts. A scheduled deployment starts automatically at the scheduled time if one of its eligible tasks is an auto task, such as HCL™ Launch tasks. Otherwise, begin a deployment by starting one of the plan's eligible tasks. If the plan contains several eligible tasks, you can start any of them. You can manually start a deployment at any time. You can manually start a scheduled deployment before its scheduled time.

The deployment plan's execution pattern determines when tasks are eligible to start. If the plan has the sequential execution pattern, which is the default pattern, tasks become eligible in the order in which they are listed in the plan, starting with the first task. After the first task resolves, the second task becomes eligible. Start eligible manual tasks by clicking the task's Start button. Auto tasks, such as HCL Launch tasks, start automatically as soon as they become eligible.

The tasks in a group with a parallel execution pattern become eligible simultaneously. Tasks in parallel groups can be started in any order. Nested groups and tasks with ad hoc dependencies can affect the execution pattern.

You can modify a deployment plan after you start a deployment. You can add, delete, and modify tasks.

After all tasks are resolved, the deployment is complete. A task is resolved if it has a status of `Complete`, `Failed`, or `Skipped`. If you reopen a task or add a task after the deployment is complete, the deployment's status changes to `In Progress`.

Parent topic: Releasing software