Sequentially run jobs in a branch
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.
Queue workflows MergedWe 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 build...
Allow "queuing" of commits to a branch to execute in series. MergedRunning 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 Redund...
Workflows - Serialize jobs MergedThere is currently no non-hacky way to make sure we don't run multiple deploys.