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

[8.14](backport #39270) Ensure ordered DRA artifacts #39289

Merged
merged 1 commit into from
Apr 30, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 30, 2024

Proposed commit message

As things are now we allow parallel builds on the
packaging pipeline, which would result in out of order artifacts (depending on which one takes longer to finish).

This commit leverages a queue to ensure a FIFO queue for DRA artifacts using the design pattern in:
https://buildkite.com/blog/concurrency-gates

Related issues

Testing/Screenshots

Using the latest approach, I triggered two DRA main snapshot builds in succession using the env vars:

DRA_BRANCH="main"
RUN_SNAPSHOT="true"
DRY_RUN="true"

and was able to see the first one triggered proceed:

image
image

whereas the second one was paused (as desired) waiting for the snapshot concurrency group:

image

It would have been nice to trigger a staging build at the same time (which should allow one job at a time, since it's a different concurrency gate) but it's not easy given the conditionals.


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

As things are now we allow parallel builds on the
packaging pipeline, which could result in out of order
artifacts (depending on which one takes longer to finish).

This commit implements two "queues" (snapshot/staging)
to ensure ordered builds of DRA artifacts.

Relates https://github.com/elastic/ingest-dev/issues/3095

(cherry picked from commit d275f27)
@mergify mergify bot requested a review from a team as a code owner April 30, 2024 08:37
@mergify mergify bot added the backport label Apr 30, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 30, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 30, 2024
@dliappis dliappis added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 30, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 30, 2024
@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 38 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

@dliappis dliappis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as it's a clean backport

@dliappis dliappis merged commit badee7a into 8.14 Apr 30, 2024
11 of 12 checks passed
@dliappis dliappis deleted the mergify/bp/8.14/pr-39270 branch April 30, 2024 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants