beats icon indicating copy to clipboard operation
beats copied to clipboard

DRA: Disable summary reports for dry runs

Open pazone opened this issue 1 year ago • 3 comments

Proposed commit message

DRA: Disable summary reports for dry runs.

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

  • Relates https://github.com/elastic/ingest-dev/issues/3095

Use cases

Screenshots

Logs

pazone avatar Apr 26 '24 17:04 pazone

This pull request doesn't have a Team:<team> label.

botelastic[bot] avatar Apr 26 '24 17:04 botelastic[bot]

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @pazone? 🙏. 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

mergify[bot] avatar Apr 26 '24 17:04 mergify[bot]

:green_heart: 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

  • Start Time: 2024-04-30T07:39:03.763+0000

  • Duration: 14 min 46 sec

Test stats :test_tube:

Test Results
Failed 0
Passed 2
Skipped 0
Total 2

:green_heart: Flaky test report

Tests succeeded.

: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 avatar Apr 26 '24 17:04 elasticmachine