-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Migrate xpack filebeat pipeline #38420
Migrate xpack filebeat pipeline #38420
Conversation
This pull request doesn't have a |
…beats into migrate-xpack-filebeat-pipeline
💔 Build Failed
Failed CI StepsHistory
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
/test x-pack/metricbeat for aws cloud |
💚 Build Succeeded
History
cc @sharbuz |
💔 Build Failed
Failed CI StepsHistory
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
💚 Build Succeeded
History
cc @sharbuz |
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
IMAGE_WIN_11: "family/general-windows-11" | ||
IMAGE_WIN_2016: "family/core-windows-2016" | ||
IMAGE_WIN_2019: "family/core-windows-2019" | ||
IMAGE_WIN_2022: "family/core-windows-2022" |
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.
We'll be switching to our custom VM images at a later stage?
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 would prefer to switch to our images at one time, at the end of the main part of the migration, when we have all green pipelines and then we'll compare the result. It will be easier to troubleshoot.
/test |
* migrate x-pack/filebeat pipeline * add generate_xxx.sh script * add aws condition * add MODULE * change images * fix MODULE_DIR and add nmap * add AWS credentials * change instance config * test * revert test (cherry picked from commit 22af217)
* migrate x-pack/filebeat pipeline * add generate_xxx.sh script * add aws condition * add MODULE * change images * fix MODULE_DIR and add nmap * add AWS credentials * change instance config * test * revert test (cherry picked from commit 22af217)
* migrate x-pack/filebeat pipeline * add generate_xxx.sh script * add aws condition * add MODULE * change images * fix MODULE_DIR and add nmap * add AWS credentials * change instance config * test * revert test (cherry picked from commit 22af217)
* Migrate xpack filebeat pipeline (#38420) * migrate x-pack/filebeat pipeline * add generate_xxx.sh script * add aws condition * add MODULE * change images * fix MODULE_DIR and add nmap * add AWS credentials * change instance config * test * revert test (cherry picked from commit 22af217) * Update pre-command * Update common.sh --------- Co-authored-by: sharbuz <[email protected]>
* Migrate xpack filebeat pipeline (#38420) * migrate x-pack/filebeat pipeline * add generate_xxx.sh script * add aws condition * add MODULE * change images * fix MODULE_DIR and add nmap * add AWS credentials * change instance config * test * revert test (cherry picked from commit 22af217) * Update pre-command * Update common.sh --------- Co-authored-by: sharbuz <[email protected]>
* Migrate xpack filebeat pipeline (#38420) * migrate x-pack/filebeat pipeline * add generate_xxx.sh script * add aws condition * add MODULE * change images * fix MODULE_DIR and add nmap * add AWS credentials * change instance config * test * revert test (cherry picked from commit 22af217) * Update pre-command * Update common.sh --------- Co-authored-by: sharbuz <[email protected]>
What is the problem this PR solves?
Jenkins->Buildkite pipelines migration
Migrate
x-pack filebeat
pipelineExample of the pipelines:
https://buildkite.com/elastic/beats-xpack-filebeat/builds/230
Examples of the affected pipelines:
beats-libbeat
beats-metricbeat
beats-packetbeat
beats-winlogbeat
beats-xpack-auditbeat
beats-xpack-dockerlogbeat
beats-xpack-libbeat
beats-xpack-metricbeat - there is an issue that was absent when the pipeline was migrated and it looks like the issue doesn't depend on the PR's changes
beats-xpack-packetbeat
beats-xpack-winlogbeat
Related issues
https://github.com/elastic/ingest-dev/issues/1693
https://github.com/elastic/ingest-dev/issues/2993 - related to MODULE