Snapshot packaging stage migration

[oakrizan]

Proposed commit message

Beats migration to Buildkite issue: https://github.com/elastic/ingest-dev/issues/1693 Links to BK builds:

• Filebeat: https://buildkite.com/elastic/filebeat/builds?branch=oakrizan%3Afilebeat-packaging-stage-migration
• Auditbeat: https://buildkite.com/elastic/auditbeat/builds?branch=oakrizan%3Afilebeat-packaging-stage-migration
• Heartbeat: https://buildkite.com/elastic/heartbeat/builds?branch=oakrizan%3Afilebeat-packaging-stage-migration

Checklist

• [x] My code follows the style guidelines of this project
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[mergify[bot]]

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @oakrizan? 🙏. For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 7 min 40 sec

Pipeline error

This error is likely related to the pipeline itself. Click here and then you will see the error (either incorrect syntax or an invalid configuration).

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: 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!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 33 min 40 sec

:robot: 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!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 33 min 2 sec

:robot: 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!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 70 min 37 sec

:robot: 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!)

[elasticmachine]

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 177 min 18 sec

Pipeline error

This error is likely related to the pipeline itself. Click here and then you will see the error (either incorrect syntax or an invalid configuration).

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: 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!)

[elasticmachine]

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-02-02T08:14:10.437+0000

• Duration: 12 min 5 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	3
Skipped	0
Total	3

:robot: 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!)

[elasticmachine]

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-02-02T09:20:32.873+0000

• Duration: 6 min 20 sec

Steps errors

Expand to view the steps failures

Check out from version control

• Took 0 min 25 sec . View more details here
• Description: [2024-02-02T09:25:05.753Z] The recommended git tool is: git [2024-02-02T09:25:05.767Z] using creden

Check out from version control

• Took 0 min 25 sec . View more details here
• Description: [2024-02-02T09:25:40.908Z] The recommended git tool is: git [2024-02-02T09:25:40.923Z] using creden

Check out from version control

• Took 0 min 25 sec . View more details here
• Description: [2024-02-02T09:26:16.073Z] The recommended git tool is: git [2024-02-02T09:26:16.087Z] using creden

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: 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!)

[elasticmachine]

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-02-02T08:20:49.198+0000

• Duration: 67 min 7 sec

Test stats :test_tube:

Test	Results
Failed	1
Passed	27985
Skipped	2009
Total	29995

Test errors

Expand to view the tests failures

Build&Test / metricbeat-pythonIntegTest / test_connection – metricbeat.module.zookeeper.test_zookeeper.ZooKeeperMntrTest_1

Expand to view the error details

 AssertionError: 2 != 1 

Expand to view the stacktrace

 self = <test_zookeeper.ZooKeeperMntrTest_1 testMethod=test_connection>

    @unittest.skipUnless(metricbeat.INTEGRATION_TESTS, "integration test")
    @pytest.mark.tag('integration')
    def test_connection(self):
        """
        ZooKeeper server module outputs an event.
        """
        self.render_config_template(modules=[{
            "name": "zookeeper",
            "metricsets": ["connection"],
            "hosts": self.get_hosts(),
            "period": "5s"
        }])
        proc = self.start_beat()
        self.wait_until(lambda: self.output_lines() > 0)
        proc.check_kill_and_wait()
        self.assert_no_logged_warnings()
    
        output = self.read_output_json()
>       self.assertEqual(len(output), 1)
E       AssertionError: 2 != 1

module/zookeeper/test_zookeeper.py:102: AssertionError 

Steps errors

Expand to view the steps failures

metricbeat-pythonIntegTest - mage pythonIntegTest

• Took 31 min 29 sec . View more details here
• Description: mage pythonIntegTest

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'org.jenkinsci.plugins.workflow.steps.FlowInterruptedException'

:robot: 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!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 29 min 29 sec

:robot: 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!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 22 min 0 sec

:robot: 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!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 58 min 17 sec

:robot: 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!)

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b filebeat-packaging-stage-migration upstream/filebeat-packaging-stage-migration
git merge upstream/main
git push upstream filebeat-packaging-stage-migration

[elasticmachine]

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 5 min 55 sec

Pipeline error

This error is likely related to the pipeline itself. Click here and then you will see the error (either incorrect syntax or an invalid configuration).

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: 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!)

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b filebeat-packaging-stage-migration upstream/filebeat-packaging-stage-migration
git merge upstream/main
git push upstream filebeat-packaging-stage-migration

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b filebeat-packaging-stage-migration upstream/filebeat-packaging-stage-migration
git merge upstream/main
git push upstream filebeat-packaging-stage-migration

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b filebeat-packaging-stage-migration upstream/filebeat-packaging-stage-migration
git merge upstream/main
git push upstream filebeat-packaging-stage-migration

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b filebeat-packaging-stage-migration upstream/filebeat-packaging-stage-migration
git merge upstream/main
git push upstream filebeat-packaging-stage-migration

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b filebeat-packaging-stage-migration upstream/filebeat-packaging-stage-migration
git merge upstream/main
git push upstream filebeat-packaging-stage-migration

[oakrizan]

/test filebeat

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b filebeat-packaging-stage-migration upstream/filebeat-packaging-stage-migration
git merge upstream/main
git push upstream filebeat-packaging-stage-migration

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 650fac7748e6de1ef5e2a7a64f19f7cf8cd7943a

History

• :green_heart: Build #2367 succeeded 60dce6408878d43bfbd2ad2a843f06bdac1a754a
• :green_heart: Build #2363 succeeded 389ddc68011fb21b6146e57fb93e27564803e376
• :green_heart: Build #2339 succeeded c17ec46fc047747e2d19ead5ea383cb1ca9c261d
• :green_heart: Build #2321 succeeded f3a16eb97d17f35e5ffe991de517cc594276616b
• :green_heart: Build #2310 succeeded 59d8cdeaf4b630bb04bc6a59f4b42aa8e0bb4093
• :green_heart: Build #2300 succeeded 9fbf70a43182f7ad47f65067047050ba3d5dc7a1

cc @oakrizan

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 650fac7748e6de1ef5e2a7a64f19f7cf8cd7943a

History

• :green_heart: Build #1137 succeeded 60dce6408878d43bfbd2ad2a843f06bdac1a754a
• :green_heart: Build #1133 succeeded 389ddc68011fb21b6146e57fb93e27564803e376
• :green_heart: Build #1109 succeeded c17ec46fc047747e2d19ead5ea383cb1ca9c261d
• :green_heart: Build #1091 succeeded f3a16eb97d17f35e5ffe991de517cc594276616b
• :green_heart: Build #1080 succeeded 59d8cdeaf4b630bb04bc6a59f4b42aa8e0bb4093
• :green_heart: Build #1070 succeeded 9fbf70a43182f7ad47f65067047050ba3d5dc7a1

cc @oakrizan

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 650fac7748e6de1ef5e2a7a64f19f7cf8cd7943a

History

• :green_heart: Build #1095 succeeded 60dce6408878d43bfbd2ad2a843f06bdac1a754a
• :green_heart: Build #1091 succeeded 389ddc68011fb21b6146e57fb93e27564803e376
• :green_heart: Build #1067 succeeded c17ec46fc047747e2d19ead5ea383cb1ca9c261d
• :green_heart: Build #1049 succeeded f3a16eb97d17f35e5ffe991de517cc594276616b
• :green_heart: Build #1038 succeeded 59d8cdeaf4b630bb04bc6a59f4b42aa8e0bb4093
• :green_heart: Build #1028 succeeded 9fbf70a43182f7ad47f65067047050ba3d5dc7a1

cc @oakrizan

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 650fac7748e6de1ef5e2a7a64f19f7cf8cd7943a

History

• :green_heart: Build #2374 succeeded 60dce6408878d43bfbd2ad2a843f06bdac1a754a
• :green_heart: Build #2370 succeeded 389ddc68011fb21b6146e57fb93e27564803e376
• :green_heart: Build #2346 succeeded c17ec46fc047747e2d19ead5ea383cb1ca9c261d
• :green_heart: Build #2328 succeeded f3a16eb97d17f35e5ffe991de517cc594276616b
• :green_heart: Build #2317 succeeded 59d8cdeaf4b630bb04bc6a59f4b42aa8e0bb4093
• :broken_heart: Build #2307 failed 9fbf70a43182f7ad47f65067047050ba3d5dc7a1

cc @oakrizan

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 650fac7748e6de1ef5e2a7a64f19f7cf8cd7943a

History

• :green_heart: Build #1092 succeeded 60dce6408878d43bfbd2ad2a843f06bdac1a754a
• :green_heart: Build #1088 succeeded 389ddc68011fb21b6146e57fb93e27564803e376
• :green_heart: Build #1064 succeeded c17ec46fc047747e2d19ead5ea383cb1ca9c261d
• :green_heart: Build #1046 succeeded f3a16eb97d17f35e5ffe991de517cc594276616b
• :green_heart: Build #1035 succeeded 59d8cdeaf4b630bb04bc6a59f4b42aa8e0bb4093
• :green_heart: Build #1025 succeeded 9fbf70a43182f7ad47f65067047050ba3d5dc7a1

cc @oakrizan

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 650fac7748e6de1ef5e2a7a64f19f7cf8cd7943a

History

• :green_heart: Build #1530 succeeded 60dce6408878d43bfbd2ad2a843f06bdac1a754a
• :green_heart: Build #1526 succeeded 389ddc68011fb21b6146e57fb93e27564803e376
• :green_heart: Build #1502 succeeded c17ec46fc047747e2d19ead5ea383cb1ca9c261d
• :green_heart: Build #1484 succeeded f3a16eb97d17f35e5ffe991de517cc594276616b
• :green_heart: Build #1473 succeeded 59d8cdeaf4b630bb04bc6a59f4b42aa8e0bb4093
• :green_heart: Build #1463 succeeded 9fbf70a43182f7ad47f65067047050ba3d5dc7a1

cc @oakrizan

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 650fac7748e6de1ef5e2a7a64f19f7cf8cd7943a

History

• :green_heart: Build #4017 succeeded 60dce6408878d43bfbd2ad2a843f06bdac1a754a
• :green_heart: Build #4013 succeeded 389ddc68011fb21b6146e57fb93e27564803e376
• :green_heart: Build #3989 succeeded c17ec46fc047747e2d19ead5ea383cb1ca9c261d
• :green_heart: Build #3971 succeeded f3a16eb97d17f35e5ffe991de517cc594276616b
• :green_heart: Build #3960 succeeded 59d8cdeaf4b630bb04bc6a59f4b42aa8e0bb4093
• :broken_heart: Build #3958 failed bafb3a40c1beb9f6f73c11e10e79bf5996a25ddc

cc @oakrizan

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 650fac7748e6de1ef5e2a7a64f19f7cf8cd7943a

History

• :green_heart: Build #1105 succeeded 60dce6408878d43bfbd2ad2a843f06bdac1a754a
• :green_heart: Build #1101 succeeded 389ddc68011fb21b6146e57fb93e27564803e376
• :green_heart: Build #1077 succeeded c17ec46fc047747e2d19ead5ea383cb1ca9c261d
• :broken_heart: Build #1059 failed f3a16eb97d17f35e5ffe991de517cc594276616b
• :green_heart: Build #1048 succeeded 59d8cdeaf4b630bb04bc6a59f4b42aa8e0bb4093
• :green_heart: Build #1038 succeeded 9fbf70a43182f7ad47f65067047050ba3d5dc7a1

cc @oakrizan