[CI] Print ES docker images versions #186885
Merged
+265
−19
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
delanni
force-pushed
the
print-more-es-serverless-info
branch
2 times, most recently
from
30214e5
to
45990d4
Compare
…buildkite annotation
delanni
force-pushed
the
print-more-es-serverless-info
branch
from
45990d4
to
10134fa
Compare
delanni
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
jbudz
approved these changes
Jun 26, 2024
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
delanni
added a commit
to delanni/kibana
that referenced
this pull request
Jun 28, 2024
## Summary When we're seeing errors in FTR or on the serverless verification pipeline, we have difficulty connecting back what version of ES-Serverless is behind the tag `:latest`. With a recent addition to the ES Serverless docker image, this info is now contained in labels of the image. This PR highlights this info in the verification pipeline, as well as the FTR output from `kbn-es`. - Serverless verification pipeline: https://buildkite.com/elastic/kibana-elasticsearch-serverless-verify-and-promote/builds/1454 - FTR:  (cherry picked from commit c9d2b70) # Conflicts: # .buildkite/pipelines/es_serverless/verify_es_serverless_image.yml
💚 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
the
backport missing
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
delanni
added
backport:skip
kibanamachine
removed
the
backport missing
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.
Summary
When we're seeing errors in FTR or on the serverless verification pipeline, we have difficulty connecting back what version of ES-Serverless is behind the tag
:latest.With a recent addition to the ES Serverless docker image, this info is now contained in labels of the image.
This PR highlights this info in the verification pipeline, as well as the FTR output from
kbn-es.Closes: https://github.com/elastic/kibana-operations/issues/136