At my job, we recently converted some pipelines to be “all-in-one.” So when a merge to main happens, the pipeline has multiple stages for building –> deploy to lower environments –> deploy to production. The production deployment requires manual approval. As a result, builds will often sit at this stage as we only deploy on a certain cadence.

As part of our trigger in the YAML file, we have batch: true. However, I believe this is causing all new merges to NOT automatically kick off the pipeline because we typically have prior runs that are sitting on the production deployment stages waiting for approval, so they technically haven’t “completed” yet.

We really only need to batch based on the build stage, not the pipeline entirely. I found this thread from 2019 detailing this same issue. A response from a Microsoft rep says “We do have per-stage batching on the backlog and plan to work on it in the next few months” – it’s been ~5 years since this post. I’m finding nothing on per-stage batching….does anyone know if this is possible?