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.

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

Snapshot packaging stage migration #37827

Merged
merged 31 commits into from
Mar 20, 2024

Conversation

oakrizan
Copy link
Contributor

@oakrizan oakrizan commented Feb 1, 2024

Proposed commit message

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

Disabled several tests on Windows when running on BK. Related issue: https://github.com/elastic/ingest-dev/issues/3016

Checklist

  • 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

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 1, 2024
Copy link
Contributor

mergify bot commented Feb 1, 2024

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

@oakrizan oakrizan added backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.12.0 Automated backport with mergify labels Feb 1, 2024
@oakrizan oakrizan force-pushed the filebeat-packaging-stage-migration branch 4 times, most recently from 0f2dc0c to 6907c12 Compare February 1, 2024 17:42
@elasticmachine
Copy link
Collaborator

💔 Build Failed

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: 7 min 40 sec

Pipeline error 1

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).

❕ 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!)

@elasticmachine
Copy link
Collaborator

❕ 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
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Duration: 33 min 40 sec

🤖 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
Copy link
Collaborator

❕ 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
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Duration: 33 min 2 sec

🤖 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!)

@oakrizan oakrizan force-pushed the filebeat-packaging-stage-migration branch from 6907c12 to 8230921 Compare February 1, 2024 18:46
@elasticmachine
Copy link
Collaborator

❕ 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
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Duration: 70 min 37 sec

🤖 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
Copy link
Collaborator

💔 Build Failed

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: 177 min 18 sec

Pipeline error 1

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).

❕ 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!)

@oakrizan oakrizan force-pushed the filebeat-packaging-stage-migration branch 2 times, most recently from 2df811d to 826eed3 Compare February 2, 2024 08:20
@elasticmachine
Copy link
Collaborator

❕ 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
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

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

  • Duration: 12 min 5 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

🤖 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!)

@oakrizan oakrizan force-pushed the filebeat-packaging-stage-migration branch 2 times, most recently from e077857 to 9b97282 Compare February 2, 2024 09:25
@elasticmachine
Copy link
Collaborator

💔 Build Failed

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

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

  • Duration: 6 min 20 sec

Steps errors 3

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

❕ 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!)

@elasticmachine
Copy link
Collaborator

❕ 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
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

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

  • Duration: 67 min 7 sec

Test stats 🧪

Test Results
Failed 1
Passed 27985
Skipped 2009
Total 29995

Test errors 1

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 2

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'

🤖 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!)

@oakrizan oakrizan force-pushed the filebeat-packaging-stage-migration branch 2 times, most recently from 81aa35f to 2fbd72c Compare February 2, 2024 09:47
@elasticmachine
Copy link
Collaborator

❕ 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
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Duration: 29 min 29 sec

🤖 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!)

@oakrizan oakrizan force-pushed the filebeat-packaging-stage-migration branch from 2fbd72c to ab651b0 Compare February 2, 2024 09:55
@elasticmachine
Copy link
Collaborator

❕ 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
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Duration: 22 min 0 sec

🤖 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
Copy link
Collaborator

❕ 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
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Duration: 58 min 17 sec

🤖 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!)

Copy link
Contributor

mergify bot commented Feb 2, 2024

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
Copy link
Collaborator

elasticmachine commented Feb 2, 2024

💔 Build Failed

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: 5 min 55 sec

Pipeline error 1

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).

❕ 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!)

@oakrizan oakrizan force-pushed the filebeat-packaging-stage-migration branch from 60dce64 to 650fac7 Compare March 20, 2024 07:42
@jlind23 jlind23 disabled auto-merge March 20, 2024 07:44
@jlind23 jlind23 merged commit 01f5a90 into elastic:main Mar 20, 2024
21 of 33 checks passed
mergify bot pushed a commit that referenced this pull request Mar 20, 2024
mergify bot pushed a commit that referenced this pull request Mar 20, 2024
(cherry picked from commit 01f5a90)

# Conflicts:
#	.buildkite/filebeat/scripts/package-step.sh
#	.buildkite/heartbeat/scripts/package-step.sh
#	.buildkite/scripts/packaging/package-step.sh
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @oakrizan

oakrizan added a commit that referenced this pull request Mar 20, 2024
(cherry picked from commit 01f5a90)

Co-authored-by: Olga Naydyonock <olga.naidjonoka@elastic.co>
oakrizan added a commit that referenced this pull request Mar 20, 2024
* Snapshot packaging stage migration (#37827)

(cherry picked from commit 01f5a90)

* fixed git conflict

---------

Co-authored-by: Olga Naydyonock <olga.naidjonoka@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.13.0 Automated backport with mergify enhancement Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants