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

[7.17](backport #39298) Branch specific concurrency gates #39303

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 30, 2024

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:

image

Blocked second run (as expected):

image


This is an automatic backport of pull request #39298 done by [Mergify](https://mergify.com).

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 mergify bot requested a review from a team as a code owner April 30, 2024 11:55
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Apr 30, 2024
Copy link
Contributor Author

mergify bot commented Apr 30, 2024

Cherry-pick of 40c68cf has failed:

On branch mergify/bp/7.17/pr-39298
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit 40c68cf2e1.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   .buildkite/packaging.pipeline.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 30, 2024
@botelastic
Copy link

botelastic bot commented Apr 30, 2024

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 14 min 49 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link
Contributor Author

mergify bot commented May 6, 2024

This pull request has not been merged yet. Could you please review and merge it @dliappis? 🙏

@dliappis
Copy link
Contributor

dliappis commented May 7, 2024

Closing as it's already done in #39197 (comment)

@dliappis dliappis closed this May 7, 2024
@mergify mergify bot deleted the mergify/bp/7.17/pr-39298 branch May 7, 2024 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants