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
refactor conditions #37999
refactor conditions #37999
Conversation
This pull request doesn't have a |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
|
/test libbeat |
.buildkite/pipeline.yml
Outdated
async: true | ||
build: | ||
env: | ||
BUILDKITE_REFSPEC: "refs/pull/${BUILDKITE_PULL_REQUEST}/head" |
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.
What's the plan for supporting branches?
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.
When the PR is approved to merge I'll remove trigger steps from the main pipeline
I guess that's the answer
Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
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.
LGTM
[ -z "${run_libbeat_arm_tests+x}" ] && run_libbeat_arm_tests="$(buildkite-agent meta-data get run_libbeat_arm_tests --default "false")" | ||
[ -z "${run_packetbeat_arm_tests+x}" ] && run_packetbeat_arm_tests="$(buildkite-agent meta-data get run_packetbeat_arm_tests --default "false")" | ||
[ -z "${run_metricbeat_macos_tests+x}" ] && run_metricbeat_macos_tests="$(buildkite-agent meta-data get run_metricbeat_macos_tests --default "false")" | ||
[ -z "${run_packetbeat_macos_tests+x}" ] && run_packetbeat_macos_tests="$(buildkite-agent meta-data get run_packetbeat_macos_tests --default "false")" |
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.
In a future PR, we should refactor this, such that if a user attempts to run this manually over ssh, it's enough to set one of the variables e.g. export run_libbeat=true
to ensure only the corresponding test runs.
As it is now, if a user only sets export run_libbeat=true
, the remaining code will invoke buildkite-agent meta-data get run_<beatname>
which will fail when not run via Buildkite.
…b.com:sharbuz/beats into refactor-congitions-and-migrate-xpack-libbeat
💚 Build Succeeded
History
cc @sharbuz |
💔 Build Failed
Failed CI StepsHistory
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
💔 Build Failed
Failed CI StepsHistory
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
(cherry picked from commit 4163848)
(cherry picked from commit 4163848)
(cherry picked from commit 4163848)
What is the problem this PR solves?
Jenkins->Buildkite pipelines migration
Refactor common conditions to simplify adding new pipelines
Examples of the affected pipelines:
https://buildkite.com/elastic/beats-libbeat/builds/1356#018da65f-3d77-4dc6-a2c0-0bbc5f7d54f4
https://buildkite.com/elastic/beats-metricbeat/builds/2570#018da65f-40e1-4bcf-b828-2b6b961c770a
https://buildkite.com/elastic/beats-packetbeat/builds/1350#018da65f-4cc7-40fe-86d7-52512d2c68e2
https://buildkite.com/elastic/beats-winlogbeat/builds/520#018da65f-23ab-4ff9-9742-4351fed8ed05
When the PR is approved to merge I'll remove trigger steps from the main pipeline
Related issues
https://github.com/elastic/ingest-dev/issues/1693