Subqueues in Pipelines
Hey all, bit of context: I have a generic pipeline that deploys all my services. This works well, but given only one run of a pipeline can be performed at a time, it leads to sequential runs when they could be parallelised (to give a concrete example: a deploy to service A's staging environment will block a deploy to service B's UAT environment).
I'd like to opt in to some control in the pipeline run and provide a lock token of some kind (which would in my case probably be a string that combines the target environment and target cluster, say, to guarantee only one run can touch service A's staging environment at a time, for example).
- Jake Warner...
Hey Thomas,
This is now done -- will go live in next update!
- Alexander Mattoni...
Hi Thomas,
I've updated our documentation to describe sub-queuing and a new trigger key page that describes how to initiate a pipeline run with a sub-queue.
https://cycle.io/docs/platform/introduction-to-pipelines#sub-queueing-parallelizing-dynamic-pipelines
- Thomas van der Pol...
This is excellent, thank you all!
Join the conversation
Sign in with your Cycle account to reply to this thread.