Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[8.13](backport #39087) Migrate packetbeat to static Buildkite pipeline #39109

Merged
merged 2 commits into from Apr 22, 2024
Merged

[8.13](backport #39087) Migrate packetbeat to static Buildkite pipeline #39109

merged 2 commits into from Apr 22, 2024

Conversation

dliappis
Copy link
Contributor

@dliappis dliappis commented Apr 22, 2024 •
edited

Proposed commit message

This commit refactors the packetbeat pipeline to the pipeline selector
approach as laid out in #38783.

Related issues

Logs

Cherry-picked from 8f8f313

Footnotes

  1. note failures for x-pack/fileabeat and x-pack/metricbeat are unrelated (flaky tests) ↩

@dliappis
Migrate packetbeat to static Buildkite pipeline (elastic#39087)
473a851 
This commit refactors the packetbeat pipeline to the pipeline selector
approach as laid out in elastic#38783.

Relates elastic/ingest-dev#3072
@dliappis dliappis self-assigned this Apr 22, 2024
@dliappis dliappis requested a review from a team as a code owner April 22, 2024 11:15
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Apr 22, 2024
This was referenced Apr 22, 2024
Closed
Merged
@dliappis dliappis changed the title Backport packetbeat #39087 to 8.13 [8.13](backport #39087) Migrate packetbeat to static Buildkite pipeline Apr 22, 2024
@elasticmachine
Copy link
Collaborator

elasticmachine commented Apr 22, 2024 •
edited

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 13 min 36 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@dliappis dliappis added arm Enable builds in the CI for ARM testing macOS Enable builds in the CI for darwin testing :Windows aws Enable builds in the CI for aws cloud testing labels Apr 22, 2024
@dliappis
Copy link
Contributor Author

@pkoutsovasilis similar comment as in #39108 (comment) for auditbeat unit test flakiness

@dliappis dliappis merged commit be1e370 into elastic:8.13 Apr 22, 2024
163 of 170 checks passed
@pkoutsovasilis
Copy link
Contributor

So far running on my local Ubuntu 22.04.4 LTS VM I can't reproduce this error. still looking 👀

This was referenced Apr 22, 2024
Closed
Merged
This was referenced Apr 26, 2024
Merged
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alexsapran alexsapran alexsapran approved these changes

Assignees

@dliappis dliappis

Labels
arm Enable builds in the CI for ARM testing aws Enable builds in the CI for aws cloud testing backport macOS Enable builds in the CI for darwin testing Team:Ingest-EngProd :Windows
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@dliappis @elasticmachine @pkoutsovasilis @alexsapran