Add Independent Agent alternate upload step in pipeline #287
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
dliappis
approved these changes
Jul 12, 2024
| # | ||
| # This is a much easier way to pull back artifacts from a triggered build than using | ||
| # a Buildkite token that we then have to manage via vault, etc. | ||
| # See: https://forum.buildkite.community/t/how-to-download-artifacts-back-from-triggered-pipeline/3480/2 |
cmacknz
approved these changes
Jul 12, 2024
dwhyrock
added a commit
that referenced
this pull request
Jul 12, 2024
* Add Independent Agent alternate upload step in pipeline * empty commit to trigger CI
dwhyrock
added a commit
that referenced
this pull request
Jul 12, 2024
* Add Independent Agent alternate upload step in pipeline * empty commit to trigger CI
dliappis
pushed a commit
that referenced
this pull request
Jul 15, 2024
…#288) Backport of #287 This PR adds an alternate step in the elastic-stack-installers that the Independent Agent Release will use in order to get only the Elastic Agent windows installer (.msi) built. The new pipeline step uses a new script that does the following: Retrieve the MSI artifacts from the Build step Moves the MSI artifacts to a new directory Creates a .sha512 file for the MSI file Saves the MSI and .sha512 artifacts using Buildkite's built-in upload functionality Sets metadata in the calling pipeline if the TRIGGER_JOB_ID is set The calling pipeline will then use this metadata to download the saved artifacts
dliappis
pushed a commit
that referenced
this pull request
Jul 15, 2024
…#289) Backport of #287 This PR adds an alternate step in the elastic-stack-installers that the Independent Agent Release will use in order to get only the Elastic Agent windows installer (.msi) built. The new pipeline step uses a new script that does the following: Retrieve the MSI artifacts from the Build step Moves the MSI artifacts to a new directory Creates a .sha512 file for the MSI file Saves the MSI and .sha512 artifacts using Buildkite's built-in upload functionality Sets metadata in the calling pipeline if the TRIGGER_JOB_ID is set The calling pipeline will then use this metadata to download the saved artifacts Merged, bypassing checks due to #277
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 PR adds an alternate step in the
elastic-stack-installersthat the Independent Agent Release will use in order to get only the Elastic Agent windows installer (.msi) built.The new pipeline step uses a new script that does the following:
.sha512file for the MSI file.sha512artifacts using Buildkite's built-in upload functionalityTRIGGER_JOB_IDis setThis PR incorporates the changes from these two PRs, which should be closed in favor of this PR:
This PR is being used instead of the "fork" version: #286