-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Branch specific concurrency gates #39298
Merged
dliappis
merged 1 commit into
elastic:main
from
dliappis:dedicate-concurrency-gate-per-branch
Apr 30, 2024
Merged
Branch specific concurrency gates #39298
dliappis
merged 1 commit into
elastic:main
from
dliappis:dedicate-concurrency-gate-per-branch
Apr 30, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PR elastic#39293 introduced one concurrency queue per staging/snapshot but this slows down unnecessarily concurrent DRA builds for main and other release branches. This commit makes the concurrency gates specific per branch.
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Apr 30, 2024
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
alexsapran
approved these changes
Apr 30, 2024
dliappis
added
backport-7.17
Automated backport to the 7.17 branch with mergify
backport-v8.13.0
Automated backport with mergify
backport-v8.14.0
Automated backport with mergify
labels
Apr 30, 2024
mergify bot
pushed a commit
that referenced
this pull request
Apr 30, 2024
PR #39293 introduced one concurrency queue per staging/snapshot but this slows down unnecessarily concurrent DRA builds for main and other release branches. This commit makes the concurrency gates (additionally) specific per branch. (cherry picked from commit 40c68cf) # Conflicts: # .buildkite/packaging.pipeline.yml
mergify bot
pushed a commit
that referenced
this pull request
Apr 30, 2024
PR #39293 introduced one concurrency queue per staging/snapshot but this slows down unnecessarily concurrent DRA builds for main and other release branches. This commit makes the concurrency gates (additionally) specific per branch. (cherry picked from commit 40c68cf) # Conflicts: # .buildkite/packaging.pipeline.yml
This was referenced Apr 30, 2024
dliappis
added a commit
that referenced
this pull request
Apr 30, 2024
PR #39293 introduced one concurrency queue per staging/snapshot but this slows down unnecessarily concurrent DRA builds for main and other release branches. This commit makes the concurrency gates (additionally) specific per branch. (cherry picked from commit 40c68cf) Co-authored-by: Dimitrios Liappis <dimitrios.liappis@gmail.com>
This was referenced May 1, 2024
dliappis
added a commit
that referenced
this pull request
May 2, 2024
PR #39293 introduced one concurrency queue per staging/snapshot but this slows down unnecessarily concurrent DRA builds for main and other release branches. This commit makes the concurrency gates (additionally) specific per branch.
dliappis
added a commit
that referenced
this pull request
May 2, 2024
PR #39293 introduced one concurrency queue per staging/snapshot but this slows down unnecessarily concurrent DRA builds for main and other release branches. This commit makes the concurrency gates (additionally) specific per branch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-7.17
Automated backport to the 7.17 branch with mergify
backport-v8.13.0
Automated backport with mergify
backport-v8.14.0
Automated backport with mergify
ci
Team:Ingest-EngProd
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.
Proposed commit message
PR #39293 introduced one concurrency queue per staging/snapshot but this slows down unnecessarily concurrent DRA builds for main and other release branches.
This commit makes the concurrency gates specific per branch.
Related issues
Logs
Example run: https://buildkite.com/elastic/beats-packaging-pipeline/builds/99#018f2ed1-88f4-4f2a-9604-e29c51eba3a3
Screenshots
First run:
Blocked second run (as expected):