Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Using multispeed deployments

Updated on July 14, 2022

Achieve greater flexibility over your pipeline workflow through multiple deployments that queue in the same stage of a pipeline. With this functionality, developers can regularly merge their changes for selective testing and promotion of deployments without blocking the pipeline. This approach introduces the concept of a transition between stages requiring user input to proceed.

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.

Note: Superseded deployments are resolved and are not be available to promote to the next phase of the pipeline. This process is intended to work on the assumption that newer deployments in a pipeline are cumulative of all the changes in previous deployments.

Configuring a stage for multispeed deployment

In multispeed deployments, the pipeline queues multiple deployments after the completion of a stage, which you can use to selectively promote deployments to the next stage. This functionality relies on the underlying pipeline model, with available configuration from Deployment Manager. When all tasks within a stage are complete, the stage progresses forward by using a configuration called Transition. You can configure the transition setting to automatically move to the next stage, or wait for a user action.
  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.

Note: Deployments queue chronologically within the stage of an application pipeline. If the most recent deployment is selected for promotion, all previously queued deployments will be superseded. Any deployments that you add later are still waiting for promotion.

  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

If you are maintaining multiple pipelines across an application for a release process and leverage the deploy with an existing artifact feature, Deployment Manager 5.1 offers multispeed deployment. Simply reconfigure your pipeline with a manual transition between stages to utilize this feature. Now, you do not need to carry forward deployments with an existing artifact, as the pipeline will do this for you.

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

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us