This documentation is for Octopus Deploy Version 3.13. View other versions

Run steps in parallel

Last updated

In Octopus 2.6 we added support to run steps in parallel. Before this feature, if you wanted to deploy many packages to different servers, you had to wait for step to finish before another one could start. By being able to run steps in parallel you can cut down your deployment time considerably in some scenarios.

To run steps in Parallel, simply create a deployment process with at least 2 steps:

Then edit the second step and change its Start Trigger to Run in parallel with previous step.

After you hit save, you'll notice that the two steps are now tied up together, meaning they will run at the same time during the deployment.

Maximum parellelism

To help your Octopus Server remain stable, we have limited the maximum number of steps you can run concurrently in any given deployment to 10. You can configure any number of steps to run in parallel, and Octopus will roll through them as quickly as possible, but it will only run 10 of them at any one time.

Steps in parallel on the same Tentacle

For safety reasons, by default Octopus runs only one step at the same time on a single Tentacle. If you want to run multiple steps on a Tentacle in parallel, you'll need to enable that setting.

Steps which depend on each other

Watch out not to run steps that depend on each other in parallel. If Step2 depends on the success of Step1, it might not be the best idea to run them in parallel, but one after the other only if Step1 was successful.