I came across a pipeline builder bottleneck on if you’re deploying 1 set of output, it seems that you can’t start another deployment simultaneously until the 1st set of outputs complete. Do you know if there’s a way around this?
Just to clarify are you talking about when you:
- Deploy the pipeline
- Make edits to the pipeline
- Save those edits and deploy again but this deployment won’t run in parallel/it’s bottlenecked by the first deploy you did?
If so, can you cancel the first deployment and then run the newest deployment?
Specifically, the sequence of events are:
- I deploy a multi-output pipeline with not all of the outputs, only some of the outputs
- I wish to deploy the other outputs as well (because it was requested)
- However, this is not possible when the other outputs are in mid-deployment
Yes I can cancel the first deployment then run the newest deployment, but then we’d have to re-wait for the previous outputs. However, these take 30+ minutes on the highest build configurations and earlier today was over an hour, so strong preference towards not re-starting.
Gotcha, currently there isn’t a way around this as our backend’s deployment state machine doesn’t support simultaneous deployments (at least from the same branch)
Got it. No worries - thanks for clarifying