-
Notifications
You must be signed in to change notification settings - Fork 143
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
[8.9](backport #3046) Add buildkite pipeline to build elastic-agent binary artifacts #3129
Conversation
* Add DRA pipeline * Fix mage and go check * Force trigger * Change permissions * source bootstrap * ignore existing folder * Generate dependencies report * Split in various steps and move creds to pre-command * Fix script name * Use agent to upload artifacts * Expose env var to force publish for testing * Generalize dra-publish.sh * Use version for dependencies file * Fix dry run * Run test dra publish * Fix version * Only upload distributions * Fix glob * Only add spanshot on build * Fix permissions on downloaded artifacts * Remove test env vars * Stop calling buildkite-agent in scripts * Add vars to test * Add correct command to staging * creat local var * Create local var * Remove testing force var * Remove test vars (cherry picked from commit 30dff79) # Conflicts: # .buildkite/pipeline.elastic-agent-binary-dra.yml # .buildkite/pipeline.yml # catalog-info.yaml
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
|
🌐 Coverage report
|
After checking with @jlind23 , we are closing this backport as it should not be needed |
This is an automatic backport of pull request #3046 done by Mergify.
Cherry-pick of 30dff79 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com