Skip to content

Migrate DRA GCS publishing from Release manager to dra-prep-plugin - #8061

Open
ninalee12 wants to merge 4 commits into
elastic:mainfrom
ninalee12:dra-processing
Open

Migrate DRA GCS publishing from Release manager to dra-prep-plugin#8061
ninalee12 wants to merge 4 commits into
elastic:mainfrom
ninalee12:dra-processing

Conversation

@ninalee12

@ninalee12 ninalee12 commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Summary of your changes

Replaces the Release Manager Docker step with elastic/dra-prep-buildkite-plugin +
a trigger to unified-release-dra-processing. Part of the platform-wide Release
Manager deprecation

Related Issues

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • I have added the necessary README/documentation (if appropriate)

Test

  • run a snapshot DRA build
  • run a staging DRA build

@ninalee12
ninalee12 marked this pull request as ready for review August 20, 2026 19:51
@ninalee12
ninalee12 requested a review from a team as a code owner August 20, 2026 19:51
@mergify

mergify Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

This pull request does not have a backport label. Could you fix it @ninalee12? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

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.

1 participant