Sequentially run jobs in a branch
under review
K
Kyle Tryon
In some instances it may be that a user makes multiple commits to a branch in a short amount of time, causing multiple Workflows to execute at the same time, possibly deploying in an incorrect order. "Auto Cancel Redundant Builds" may not be suitable for all situations in which multiple deployments are expected. Solution: Enable a way to ensure that commits to a new branch are queued for sequential execution.
CCI-I-840
Fredrik A. Madsen-Malmo
Are there any updates on this project?
D
Devin Riegle
Yes, this is a necessity for deploying applications through Circle. Please add!
Chris Morris
Yes please.
(This request was put "under review" in Sept 2020, what does that mean and is it still current? I'm guessing it's not?)
B
Ben Limmer
For reference, this is how they do it in GitHub Actions: https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency
It's a pretty simple/elegant solution IMO
Jordan
We need this as well. We've seen out-of-order deploys end up taking our production state backward to an older commit, when two close-together commits happen close together.
Ideally we'd like to allow the
build
of our workflow to proceed, but then pause until it can acquire a lock of some sort to proceed with the actual deploy.Alex Sweeney
This is 100% needed for us. The queue orb is not a good hack and won't work for our use case. As our company scales, using CircleCI for CI is going to become harder and harder for us and we may have to move to some other solution. People are getting blocked by their deploys failing because of this issue and it'll only get worse as we hire more people.
I'm kind of shocked that this isn't already an option, for CI this seems like a no-brainer.
C
Caran Chris
This is a big need for us. I've brought it up with our CSM.
L
Liya Ai
under review
Merged in a post:
Queue workflows
K
Kelsey Steinbeck
We are wanting to do continuous deployments. The issue we are having is the lack of queueing. If we have two commits A and B. I need A to complete before B starts. B can’t start while A is still in progress. We don’t want to cancel redundant builds in case A is in progress. We would like to run workflows in sequential order.
CCI-I-815
Merged in a post:
Allow "queuing" of commits to a branch to execute in series.
K
Kyle Tryon
Running multiple commits within a short time period on a deploy branch may execute out of order due to small differences in execution time. For that reason, some users wish to delay subsequent commits until each job has finished.Auto-Cancel Redundant Builds is a solution for some, but not those that deploy from their main branch or users who do not wish to cancel jobs mid-build.
CCI-I-854
Load More
→