Rationalise BitBar CI concurrency group #1909
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
NOTE: Please let me merge this PR myself, it needs to be merged as the same time as several others to avoid unnecessary failures on CI.
Rationalise the Buildkite concurrency group used to control access to BitBar across all of our repos.
Design
We were using separate groups fro web and device usage, when in fact they are counted towards the same usage limit. All groups are now being renamed to simply 'bitbar' with a limit of 25.
The main mistake that I could make here is missing an instance of the old groups (
bitbar-app
andbitbar-web
, so I am using the global find and replace function of my IDE.Changeset
Buildkite concurrency group changes only.
Testing
Verified by peer review.