chore: skip system-integration scenarios for Beats#2482
chore: skip system-integration scenarios for Beats#2482mdelapenya merged 3 commits intoelastic:mainfrom
Conversation
.ci/.e2e-tests-beats.yaml
Outdated
| - name: "Linux Integration" | ||
| tags: "linux_integration" | ||
| platforms: ["debian_arm64", "debian_amd64", "sles15"] | ||
| # - name: "Permissions Output change" |
There was a problem hiding this comment.
These look to be commented out everywhere, can they just be deleted?
| - name: "Metricbeat" | ||
| tags: "metricbeat" | ||
| platforms: ["debian_amd64"] | ||
| - suite: "fleet" |
There was a problem hiding this comment.
Is the base for this from https://github.com/elastic/e2e-testing/blob/main/.ci/.e2e-tests.yaml?
Can we maybe reference that file in a comment here, and note what the differences are and why?
There was a problem hiding this comment.
About the differences, I'd like the product team to be the ones to define what to run when beats triggers the e2e for Fleet. I could see it defining different profiles: for kubernetes autodiscover, metricbeat, filebeat, etc, and with them, slect one or the other profile from beats when a a condition is met in the Beats pipeline (modified files?)
There was a problem hiding this comment.
Makes sense, I do expect us to be maintaining this after the initial commit.
* chore: copy default profile for beats * chore: remove system integrations tests for Beats * chore: remove comments (cherry picked from commit 33ea115)
* chore: copy default profile for beats * chore: remove system integrations tests for Beats * chore: remove comments (cherry picked from commit 33ea115)
* chore: copy default profile for beats * chore: remove system integrations tests for Beats * chore: remove comments (cherry picked from commit 33ea115)
* main: bump stack version 8.3.0-d380914f (elastic#2505) chore: refactor cucumber tags (elastic#2496) chore: skip system-integration scenarios for Beats (elastic#2482)
* main: bump stack version 8.3.0-d380914f (elastic#2505) chore: refactor cucumber tags (elastic#2496) chore: skip system-integration scenarios for Beats (elastic#2482)
* main: bump stack version 8.3.0-8ee1196f (elastic#2519) ci: daily pipeline to use main branch (elastic#2516) bump stack version 8.3.0-53513548 (elastic#2513) chore: run reaper daily at 1:30 am (elastic#2512) avoid aliases if no major.minor format (elastic#2501) bump stack version 8.3.0-d380914f (elastic#2505) chore: refactor cucumber tags (elastic#2496) chore: skip system-integration scenarios for Beats (elastic#2482) bump stack version 8.3.0-5c1ff35f (elastic#2494) chore: reduce AWS instances size (elastic#2477) chore: wait for the stack while provisioning (elastic#2486) bump stack version 8.3.0-6ba9f710 (elastic#2484)
What does this PR do?
It copies the default profile for running the e2e tests, removing the system-integration tests, as they are adding certain flakiness
Why is it important?
Having a more stable test execution is critical for team success, and the system integration test suite is behaving with certain flakiness, which the product team is currently investigating.
Checklist
make unit-test), and they are passing locallymake noticein the proper directory)Related issues