So long as you have enough agents, you can deploy to multiple stages in a release at the same time.įor example, suppose your collection has three parallel jobs. Parallel processing within a single release does not require additional parallel jobs. Parallel processing within a single release
#Silverstack parallel jobs not running manual
Manual intervention does not consume a job in TFS 2017.1 and newer. Release 13 cannot start because the manual intervention state consumes a parallel job. Release 11 is waiting for manual intervention.Even though Release 11 is approved, it resumes only after Release 12's deployment is completed.Release 12's deployment starts because a release waiting for approvals does not consume a parallel job. Release 12 is queued until Release 11's deployment is active.Deployment of FabrikamFiber Release 11 starts after Release 10's deployment is complete.FabrikamFiber Release 10 is first to be deployed.However, waiting for a manual intervention in the middle of a deployment does consume a parallel job. Waiting for an approval does not consume a parallel job. When additional releases are triggered, they are queued and will wait for the previous one to complete.Ī release requires a parallel job only when it is being actively deployed to a stage. This allows users in that collection to run only one release at a time.
![silverstack parallel jobs not running silverstack parallel jobs not running](https://about.gitlab.com/images/blogimages/using-run-parallel-jobs/historical-pipeline-duration.png)
![silverstack parallel jobs not running silverstack parallel jobs not running](https://forum.shotcut.org/uploads/default/original/2X/d/d31451224ba60625b57f8651e6b9841935d4e40f.png)
For example, a collection in a Team Foundation server has one parallel job.