In the example above, there is a manual transition configured when going from Quality Assurance (QA) to Staging. New deployments queue chronologically, waiting for promotion to the next stage. The user with the appropriate privilege is able to select and promote a specific deployment. In this example, Deployment #3 is selected for promotion. This automatically resolves the previous deployments, Deployment #1 and Deployment #2 (superseded). Deployment #3 is promoted to Staging and the pipeline resumes running through all of the tasks configured in the QA stage.

Configuring a stage for multispeed deployment

1. From the Deployment Manager portal, click Pipelines.
2. Select the pipeline that you want to configure for multispeed deployment.
3. On the Actions menu, select Edit pipeline.
4. Click Pipeline model.
5. Click the heading for the stage that requires manual transition, where you want deployments to queue after stage completion until selected for promotion.
6. In the stage details section, in the When all tasks in this stage are complete field, select the Wait for user action switch.
7. Click Save.

Promoting pending deployments

The pipeline modeling landing page provides a dashboard of all pending deployments within your application pipeline. From here, deployments can be selectively promoted for progression through the workflow.

1. Click Pipelines.
2. Open the pipeline that contains the deployment that you want to promote.

   The overview section shows a dashed line between stages that indicate that a manual transition is required. The Deployment History section shows this deployment with a Waiting status.

3. In the overview section, choose the action that you want to run on the deployment.

Multiple pipelines for an application

Customers migrating from 4.x versions can now leverage multispeed deployments if maintaining multiple pipelines targeting different stages for an application.