[artifacts] Remove docker cloud context verification #134046
Merged
Conversation
This file contains 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
This test was added as a verification step for daily releasable artifacts. We had originally planned on the release manager consuming this context. The expected workflow has changed now to us building and publishing the docker image instead, which already has coverage in the Build and Deploy to Cloud step.
jbudz
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
spalger
approved these changes
Jun 9, 2022
💚 Build SucceededMetrics [docs]
To update your PR or re-run it, just comment with: |
kibanamachine
pushed a commit
that referenced
this pull request
Jun 9, 2022
This test was added as a verification step for daily releasable artifacts. We had originally planned on the release manager consuming this context. The expected workflow has changed now to us building and publishing the docker image instead, which already has coverage in the Build and Deploy to Cloud step. (cherry picked from commit fa4d102)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jun 9, 2022
This test was added as a verification step for daily releasable artifacts. We had originally planned on the release manager consuming this context. The expected workflow has changed now to us building and publishing the docker image instead, which already has coverage in the Build and Deploy to Cloud step. (cherry picked from commit fa4d102) Co-authored-by: Jonathan Budzenski <[email protected]>
jbudz
added a commit
that referenced
this pull request
Jun 10, 2022
jbudz
added a commit
that referenced
this pull request
Jun 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This test was added as a verification step for daily releasable
artifacts. We had originally planned on the release manager consuming
this context. The expected workflow has changed now to us building and
publishing the docker image instead, which already has coverage in the
Build and Deploy to Cloud step.