CircleCI Ideas

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 24 2019
  • Taking votes
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    29 Mar 16:46

    A related idea that this would seem to address is that two half-finished workflows are worth a lot less than one finished workflow.  Even without deploys, I would rather have CircleCI prioritize _finishing_ a workflow that it has started over _starting_ a new workflow.  Then, instead of hanging around waiting for complete results for two different pieces of work, I can wait for less time for one result and then act on it while CircleCI is producing the second result.

  • Admin
    Kunal Jain commented
    10 Apr 21:35

    Thank you so much for your interest in this feature. Initial straw-man that we have been discussing is to have serialization at a pipeline level or rather at workflow level. If pipeline/workflows are serialized, commits would build the order they were received by CircleCI. This feature is definitely on our radar but is currently backlogged behind some refactoring work. Happy to reach out once we start working on it. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    07 May 01:43

    This problem actively discourages people from increasing their concurrency (paying circleci), I'd think it would be a huge priority.