-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add Independent Agent alternate step in pipeline #286
Conversation
.buildkite/pipeline.yml
Outdated
key: "independent-agent-staging" | ||
if: | | ||
// This should only run when triggered from Independent Agent Staging | ||
(build.env("BUILDKITE_TRIGGERED_FROM_BUILD_PIPELINE_SLUG") == "independent-agent-release-staging") || ( build.branch == 'pull/286/merge') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will remove the last clause about the PR branch once this PR is reviewed and ready to merge. Until then, we'll still use it for testing the other work related to the Windows MSI file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Someone else should probably review my original C# changes.. but i confirm they are intact.
I will follow up with some comments on the code for future readers
Closing in favor of a PR that is not from a fork: #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:
.sha512
file for the MSI file.sha512
artifacts using Buildkite's built-in upload functionalityTRIGGER_JOB_ID
is setThis PR incorporates the changes from these two PRs, which should be closed in favor of this PR:
I tested this PR with this unified-release PR, and verified that the Independent Agent Staging pipeline successfully triggers this new pipeline step, and is able to download the MSI and
.sha512
artifacts after this triggered pipeline finishes running.Example of successful execution:
elastic-stack-installers
pipeline for this PR triggered by the above pipeline: https://buildkite.com/elastic/elastic-stack-installers/builds/5635