[artifacts] Deploy Cloud image #129650
Merged
[artifacts] Deploy Cloud image #129650
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 adds the publish step to the release pipeline, which uses the release-manager CLI to upload a list Kibana artifacts.
jbudz
added
skip-ci
release_note:skip
Co-authored-by: Chris <[email protected]>
This reverts commit a6228f5.
|
Pinging @elastic/kibana-operations (Team:Operations) |
brianseeders
approved these changes
Apr 13, 2022
|
buildkite test this |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
kibanamachine
pushed a commit
that referenced
this pull request
Apr 13, 2022
* [artifacts] Publish release artifacts This adds the publish step to the release pipeline, which uses the release-manager CLI to upload a list Kibana artifacts. * cleanup * [artifacts] Test cloud image * tmp skip unrelated steps * build cloud artifact * fix tag * add missing artifacts * enable rm * fix syntax * fix tag * fix artifact * fix variable * source utils * fix path * fix version * skip steps * re-add pipeline steps * set permissions * Update .buildkite/scripts/steps/artifacts/publish.sh Co-authored-by: Chris <[email protected]> * Revert "Update .buildkite/scripts/steps/artifacts/publish.sh" This reverts commit a6228f5. * export * support version qualifier * setup env * cleanup * consistency * \n * comment * unneccessary fallback * +x * hoist env args * source * link to artifacts * fix artifacts summary * relax docker glob * \n * fix summary * fix variable * rm es docker image * setup cloud env * rename deployment * exclude skipCloud * only run on snapshot builds * update step name * TEST_BROWSER_HEADLESS=1 * cleanup * newline * consistency * pass deployment id Co-authored-by: Chris <[email protected]> (cherry picked from commit 482ae8a)
💚 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
Apr 13, 2022
* [artifacts] Publish release artifacts This adds the publish step to the release pipeline, which uses the release-manager CLI to upload a list Kibana artifacts. * cleanup * [artifacts] Test cloud image * tmp skip unrelated steps * build cloud artifact * fix tag * add missing artifacts * enable rm * fix syntax * fix tag * fix artifact * fix variable * source utils * fix path * fix version * skip steps * re-add pipeline steps * set permissions * Update .buildkite/scripts/steps/artifacts/publish.sh Co-authored-by: Chris <[email protected]> * Revert "Update .buildkite/scripts/steps/artifacts/publish.sh" This reverts commit a6228f5. * export * support version qualifier * setup env * cleanup * consistency * \n * comment * unneccessary fallback * +x * hoist env args * source * link to artifacts * fix artifacts summary * relax docker glob * \n * fix summary * fix variable * rm es docker image * setup cloud env * rename deployment * exclude skipCloud * only run on snapshot builds * update step name * TEST_BROWSER_HEADLESS=1 * cleanup * newline * consistency * pass deployment id Co-authored-by: Chris <[email protected]> (cherry picked from commit 482ae8a) Co-authored-by: Jonathan Budzenski <[email protected]>
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 adds a pipeline step to create a deployment using our Cloud image artifact. Eventually we want to run FTR tests against this deployment, but unfortunately during testing there were unexpected situations (e.g. wrong credentials) where our test runner logs were not sanitized. For now this verifies our Cloud image deploys and then shuts it down.
I think there's utility in this limited check without running the FTR. I'd like to split FTR log cleanup into a separate PR and then enable the outlined FTR setup. I'm open to postponing this merge too - opening it up for discussion.
This is only enabled for snapshot builds until we have an API for getting the correct release build for beats (which is embedded in the docker image). Beats artifacts needs to match with other stack images to qualify for a staging build.
Depends on #129499. This will be easier to review once that's merged.