[Ops] Emit trigger step, even in DRY_RUN#178707
Merged
delanni merged 1 commit intoelastic:mainfrom Mar 14, 2024
Merged
Conversation
…now prepared to handle DRY_RUN
delanni
added
Team:Operations
Contributor
|
Pinging @elastic/kibana-operations (Team:Operations) |
Member
Author
|
Foregoing approvals, this is a missed change, with little risk - admin merging to unblock myself |
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
3 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
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_RUNand we can happily trigger the downstreamgpctl-promotejob.