Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a "concurrency gate" around front-end deployments #9884

Merged
merged 5 commits into from
Jun 2, 2023

Conversation

alexwlchan
Copy link
Contributor

It took me a while to wrap my head around this, but I think I get it now.

This implements the "concurrency gate" pattern described in Buildkite's support blog here: https://buildkite.com/blog/concurrency-gates

I'm not going to explain it in the PR description, because there's a comment in the Buildkite YAML and that's the thing we'll have to follow in six months time when we're scratching our heads at this code. If I need to clarify stuff, I'll update that comment rather than this description.

This is an offshoot of the work to get e2es running on pull requests: #9876

@alexwlchan alexwlchan force-pushed the use-concurrency-gate-on-deploys branch from 0cd355e to c2c6a52 Compare June 1, 2023 06:38
@alexwlchan alexwlchan requested a review from a team June 1, 2023 10:13
remove lingering references to stage
@alexwlchan alexwlchan merged commit ff8f1ff into main Jun 2, 2023
0 of 2 checks passed
@alexwlchan alexwlchan deleted the use-concurrency-gate-on-deploys branch June 2, 2023 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants