Skip to content
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

Merged
merged 11 commits into from
Feb 15, 2022
Merged

[ci] Verify docker contexts #122897

merged 11 commits into from
Feb 15, 2022

Conversation

jbudz
Copy link
Member

@jbudz jbudz commented Jan 12, 2022

This adds a new CI step to verify our generated docker contexts by running docker build on the output.

Closes #122865

@jbudz jbudz added Team:Operations Team label for Operations Team v7.17.0 v8.0.0 v8.1.0 auto-backport Deprecated: Automatically backport this PR after it's merged release_note:skip Skip the PR/issue when compiling release notes labels Jan 13, 2022
@jbudz jbudz marked this pull request as ready for review January 13, 2022 19:28
@jbudz jbudz requested a review from a team as a code owner January 13, 2022 19:28
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@jbudz
Copy link
Member Author

jbudz commented Jan 13, 2022

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?

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@jbudz jbudz added the skip-ci label Jan 14, 2022
jbudz added a commit to jbudz/kibana-buildkite that referenced this pull request Jan 14, 2022
Adds a pipeline for the changes introduced in
elastic/kibana#122897.  This will verify that
the generated docker context builds.
@jbudz
Copy link
Member Author

jbudz commented Jan 18, 2022

@elasticmachine merge upstream

@jbudz jbudz added v7.17.1 and removed v7.17.0 labels Feb 2, 2022
@jbudz
Copy link
Member Author

jbudz commented Feb 2, 2022

@elasticmachine merge upstream

@jbudz
Copy link
Member Author

jbudz commented Feb 4, 2022

@elasticmachine merge upstream

@jbudz
Copy link
Member Author

jbudz commented Feb 8, 2022

@elasticmachine merge upstream

@tylersmalley
Copy link
Contributor

Running a build here to test.

@tylersmalley
Copy link
Contributor

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.

@jbudz
Copy link
Member Author

jbudz commented Feb 15, 2022

@elasticmachine merge upstream

@jbudz jbudz merged commit 16f3eb3 into elastic:main Feb 15, 2022
@kibanamachine
Copy link
Contributor

The following labels were identified as gaps in your version labels and will be added automatically:

  • v8.2.0

If any of these should not be on your pull request, please manually remove them.

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Feb 15, 2022
* [ci] Verify docker contexts

* bootstrap

* debug

* mkdir target

* change subdomain if snapshot

* move to separate pipeline

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 16f3eb3)
@kibanamachine
Copy link
Contributor

💔 Some backports could not be created

Status Branch Result
8.0 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.0:
- [build/docker] Replace CentOS base image with Ubuntu (#118928)
8.1
7.17 Backport failed because of merge conflicts

How to fix

Re-run the backport manually:

node scripts/backport --pr 122897

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 Feb 15, 2022
* [ci] Verify docker contexts

* bootstrap

* debug

* mkdir target

* change subdomain if snapshot

* move to separate pipeline

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 16f3eb3)

Co-authored-by: Jonathan Budzenski <jon@elastic.co>
jbudz added a commit to jbudz/kibana that referenced this pull request Feb 18, 2022
* [ci] Verify docker contexts

* bootstrap

* debug

* mkdir target

* change subdomain if snapshot

* move to separate pipeline

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
jbudz added a commit to jbudz/kibana that referenced this pull request Feb 18, 2022
* [ci] Verify docker contexts

* bootstrap

* debug

* mkdir target

* change subdomain if snapshot

* move to separate pipeline

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
jbudz added a commit that referenced this pull request Feb 18, 2022
* [ci] Verify docker contexts

* bootstrap

* debug

* mkdir target

* change subdomain if snapshot

* move to separate pipeline

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
jbudz added a commit that referenced this pull request Feb 18, 2022
* [ci] Verify docker contexts

* bootstrap

* debug

* mkdir target

* change subdomain if snapshot

* move to separate pipeline

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated: Automatically backport this PR after it's merged release_note:skip Skip the PR/issue when compiling release notes skip-ci Team:Operations Team label for Operations Team v7.17.1 v8.0.0 v8.1.0 v8.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI] Test docker build contexts
5 participants