Allow Custom Pipeline builds to be queued

Issue #16208 duplicate
Shane Fast
created an issue

So for context - we have a custom master branch pipeline that occurs each time that a pull request is merged into our master branch. In this build, once all the tests pass and all the other checks are successful we tag the commit with a version number - this certifies to our team that this commit is good to proceed to the next stage in our deployment. This provides us with certainty that each and every change we make is stable, but as you might have guessed this means that we can only process one pull request at a time.

If we merge more than one PR into master then our tagging system risks getting confused - which creates work for our team to clean up. Is there a way to allow builds using a custom pipeline to queue up rather than all running at once? Or should we rethink our entire tagging system?

Comments (2)

  1. Aneita Yang staff

    Hey Shane,

    Thanks for reaching out and for the suggestion. Your team's workflow with tagging the commit when the PR is merged to master is reasonable, so I don't think you need to worry about rethinking your workflow. We're tracking a similar request on issue #16262 - I encourage you to vote for / watch that issue if it is something that you're interested in. But, as mentioned on that issue, we're currently working on higher priority requests so it is unlikely that we'll work on this anytime soon.

  2. Log in to comment