[Ops] Propagate DRY_RUN to gpctl-promote#178658
Merged
delanni merged 2 commits intoelastic:mainfrom Mar 14, 2024
Merged
Conversation
delanni
added
release_note:skip
Contributor
|
Pinging @elastic/kibana-operations (Team:Operations) |
jbudz
approved these changes
Mar 13, 2024
delanni
added a commit
that referenced
this pull request
Mar 14, 2024
## Summary Missed adding this change in #178658 Tested in https://buildkite.com/elastic/kibana-serverless-release-1/builds/138 - the receiving pipeline is now prepared for `DRY_RUN` and we can happily trigger the downstream `gpctl-promote` job.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary
We've had some issues with the weekly scheduled serverless release after we've switched to a direct trigger to
gpctl-promote.Although we've tried a few options, and we've probably found the solution, but we can still go for sure, and try a dry-run cross trigger. This wasn't possible before, but https://github.com/elastic/gpctl/pull/261 should now respect DRY_RUN env vars coming in.
This PR propagates those variables, so we can test the setup.