[build] Add flag for using a local Kibana artifact in the Docker context #129375
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
Currently Docker contexts always install a Kibana distribution from an http endpoint. These endpoints are only available after a release has been published, making pre-release testing difficult. This adds a flag to use a local Kibana artifact, with the intention of verifying the Docker contexts with release artifacts prior to publishing the release.
jbudz
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
brianseeders
approved these changes
Apr 4, 2022
💚 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 4, 2022
…ext (#129375) * [build] Add flag for using a local Kibana artifact in the Docker context Currently Docker contexts always install a Kibana distribution from an http endpoint. These endpoints are only available after a release has been published, making pre-release testing difficult. This adds a flag to use a local Kibana artifact, with the intention of verifying the Docker contexts with release artifacts prior to publishing the release. * fix types (cherry picked from commit 4182523)
💔 Some backports could not be created
Manual backportTo create the backport manually run: 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 4, 2022
…ext (#129375) (#129393) * [build] Add flag for using a local Kibana artifact in the Docker context Currently Docker contexts always install a Kibana distribution from an http endpoint. These endpoints are only available after a release has been published, making pre-release testing difficult. This adds a flag to use a local Kibana artifact, with the intention of verifying the Docker contexts with release artifacts prior to publishing the release. * fix types (cherry picked from commit 4182523) Co-authored-by: Jonathan Budzenski <[email protected]>
jbudz
added a commit
to jbudz/kibana
that referenced
this pull request
Apr 4, 2022
…ext (elastic#129375) * [build] Add flag for using a local Kibana artifact in the Docker context Currently Docker contexts always install a Kibana distribution from an http endpoint. These endpoints are only available after a release has been published, making pre-release testing difficult. This adds a flag to use a local Kibana artifact, with the intention of verifying the Docker contexts with release artifacts prior to publishing the release. * fix types
jbudz
added a commit
that referenced
this pull request
Apr 4, 2022
…ext (#129375) (#129409) * [build] Add flag for using a local Kibana artifact in the Docker context Currently Docker contexts always install a Kibana distribution from an http endpoint. These endpoints are only available after a release has been published, making pre-release testing difficult. This adds a flag to use a local Kibana artifact, with the intention of verifying the Docker contexts with release artifacts prior to publishing the release. * fix types
|
7.17: fc7127d |
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.
Currently Docker contexts always install a Kibana distribution from an
http endpoint. These endpoints are only available after a release has
been published, making pre-release testing difficult.
This adds a flag to use a local Kibana artifact, with the intention of
verifying the Docker contexts with release artifacts prior to publishing
the release.
Testing