# Pipeline Concurrency Limit

**URL:** https://forum.buildkite.community/t/pipeline-concurrency-limit/240
**Category:** Features Requests
**Created:** [January 14, 2019, 11:24pm UTC](https://forum.buildkite.community/t/pipeline-concurrency-limit/240 "2019-01-14T23:24:30Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![jess](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/jess/32/24_2.png) [@jess](https://forum.buildkite.community/u/jess)
#### Post date: [November 12, 2020, 6:43pm UTC](https://forum.buildkite.community/t/pipeline-concurrency-limit/240/4 "2020-11-12T18:43:27Z")

</div>

Hi folks,

Apologies for the late response here, but I believe I have good news!

An option which I believe will suit your needs, but I confess we’ve not been very good at explaining is what we call [concurrency gating](https://buildkite.com/docs/pipelines/controlling-concurrency#concurrency-and-parallelization).

In short, the jobs which are part of a concurrency group within a given build which are eligible to run (i.e. not following a currently blocked block step, are not preceded by a failure) must _all_ finish before another build’s jobs in that concurrency group are permitted to run.

This means you can make a no-op or some other preparatory step (we’re using `echo` commands, but what is run in the step doesn’t matter) to denote the start of the “gate”, and another to denote the end, and anything between those two steps which share a concurrency group must finish before the gate will be reopened to other work.

Now, I must concede that this is not, explicitly, a limit on concurrent _builds_, but it is functionally more or less equivalent without tying up other resources, and works today.

I hope this helps!

---

_[View the full topic](https://forum.buildkite.community/t/pipeline-concurrency-limit/240)._