-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci] Verify docker contexts #122897
[ci] Verify docker contexts #122897
Conversation
Pinging @elastic/kibana-operations (Team:Operations) |
I'm leaning towards moving this to its own pipeline. There's not a lot of utility in running this hourly, and it depends on a snapshot download of Kibana. This may be the day after a version bump, which would cause a string of build failures. Thoughts? |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Adds a pipeline for the changes introduced in elastic/kibana#122897. This will verify that the generated docker context builds.
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Running a build here to test. |
Looks good as a stand-alone daily. Let's create a task to merge into the normal pipeline when we're done with the daily releasable artifacts and the artifact we're testing against is what we are creating. |
@elasticmachine merge upstream |
The following labels were identified as gaps in your version labels and will be added automatically:
If any of these should not be on your pull request, please manually remove them. |
* [ci] Verify docker contexts * bootstrap * debug * mkdir target * change subdomain if snapshot * move to separate pipeline Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit 16f3eb3)
💔 Some backports could not be created
How to fixRe-run the backport manually:
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
* [ci] Verify docker contexts * bootstrap * debug * mkdir target * change subdomain if snapshot * move to separate pipeline Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit 16f3eb3) Co-authored-by: Jonathan Budzenski <[email protected]>
* [ci] Verify docker contexts * bootstrap * debug * mkdir target * change subdomain if snapshot * move to separate pipeline Co-authored-by: Kibana Machine <[email protected]>
* [ci] Verify docker contexts * bootstrap * debug * mkdir target * change subdomain if snapshot * move to separate pipeline Co-authored-by: Kibana Machine <[email protected]>
* [ci] Verify docker contexts * bootstrap * debug * mkdir target * change subdomain if snapshot * move to separate pipeline Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
* [ci] Verify docker contexts * bootstrap * debug * mkdir target * change subdomain if snapshot * move to separate pipeline Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
This adds a new CI step to verify our generated docker contexts by running
docker build
on the output.Closes #122865