Skip to content

chore: use a different e2e profile for running them from Beats#31531

Merged
mdelapenya merged 2 commits intomainfrom
mdelapenya-patch-1
May 10, 2022
Merged

chore: use a different e2e profile for running them from Beats#31531
mdelapenya merged 2 commits intomainfrom
mdelapenya-patch-1

Conversation

@mdelapenya
Copy link
Copy Markdown
Contributor

@mdelapenya mdelapenya commented May 5, 2022

What does this PR do?

It passes the name of a profile that will be used to add/retire specific tests from the e2e test suite when it's called from Beats pipeline.

Why is it important?

We'd like to remove scenarios that the team consider flaky while they are investigating them, to avoid adding noise to the rest of pull-requests.

I personally don't like to skip a test without further investigation because it's easily forgotten to be re-added. On the other hand, I understand that this PR would improve the reliability of the tests, therefore the team would work more smoothly and with more confidence in the CI system.

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

  • A PR on the e2e-tests adding the test suites needs to be created

Related issues

Requires elastic/e2e-testing#2482

The e2e supports passing profile, which is used to execute a different combination of scenarios/suites to be run in different OSs/Archs
@mdelapenya mdelapenya added the Team:Automation Label for the Observability productivity team label May 5, 2022
@mdelapenya mdelapenya requested review from a team, cmacknz and v1v May 5, 2022 14:40
@mdelapenya mdelapenya self-assigned this May 5, 2022
@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 May 5, 2022
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented May 5, 2022

💚 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: 2022-05-10T10:14:09.890+0000

  • Duration: 15 min 45 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

💚 Flaky test report

Tests succeeded.

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

@mdelapenya mdelapenya marked this pull request as ready for review May 9, 2022 12:47
@mdelapenya mdelapenya requested a review from a team as a code owner May 9, 2022 12:47
@mdelapenya mdelapenya requested review from faec and removed request for a team May 9, 2022 12:47
@mdelapenya
Copy link
Copy Markdown
Contributor Author

Because the counterpart is already in place (https://github.com/elastic/e2e-testing/blob/main/.ci/.e2e-tests-beats.yaml), I'd say this is ready to go

@mdelapenya mdelapenya added backport-v8.1.0 Automated backport with mergify backport-v8.2.0 Automated backport with mergify backport-7.17 Automated backport to the 7.17 branch with mergify labels May 10, 2022
@mdelapenya mdelapenya merged commit 03b013e into main May 10, 2022
mergify bot pushed a commit that referenced this pull request May 10, 2022
* chore: use a different e2e profile for running them from Beats

The e2e supports passing profile, which is used to execute a different combination of scenarios/suites to be run in different OSs/Archs

* fix: file extension

(cherry picked from commit 03b013e)

# Conflicts:
#	.ci/packaging.groovy
mergify bot pushed a commit that referenced this pull request May 10, 2022
* chore: use a different e2e profile for running them from Beats

The e2e supports passing profile, which is used to execute a different combination of scenarios/suites to be run in different OSs/Archs

* fix: file extension

(cherry picked from commit 03b013e)

# Conflicts:
#	.ci/packaging.groovy
mergify bot pushed a commit that referenced this pull request May 10, 2022
* chore: use a different e2e profile for running them from Beats

The e2e supports passing profile, which is used to execute a different combination of scenarios/suites to be run in different OSs/Archs

* fix: file extension

(cherry picked from commit 03b013e)
rdner pushed a commit that referenced this pull request Jun 2, 2022
… them from Beats (#31573)

* chore: use a different e2e profile for running them from Beats (#31531)

* chore: use a different e2e profile for running them from Beats

The e2e supports passing profile, which is used to execute a different combination of scenarios/suites to be run in different OSs/Archs

* fix: file extension

(cherry picked from commit 03b013e)

* fix: proper filename

Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
mdelapenya added a commit that referenced this pull request Jun 15, 2022
… (#31571)

* chore: use a different e2e profile for running them from Beats

The e2e supports passing profile, which is used to execute a different combination of scenarios/suites to be run in different OSs/Archs

* fix: file extension

(cherry picked from commit 03b013e)

# Conflicts:
#	.ci/packaging.groovy

Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
chrisberkhout pushed a commit that referenced this pull request Jun 1, 2023
* chore: use a different e2e profile for running them from Beats

The e2e supports passing profile, which is used to execute a different combination of scenarios/suites to be run in different OSs/Archs

* fix: file extension
@v1v v1v deleted the mdelapenya-patch-1 branch April 8, 2025 18:52
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.1.0 Automated backport with mergify backport-v8.2.0 Automated backport with mergify Team:Automation Label for the Observability productivity team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants