[CI] [Don't merge yet] Integration tests regrouping #6349
Conversation
pazone
added
enhancement
pazone
changed the title
pazone
added
backport-8.x
| if os.Getenv("BUILDKITE_PULL_REQUEST") != "" { | ||
| return 50 | ||
| } |
There was a problem hiding this comment.
This deserves a comment in my opinion.
| @@ -40,8 +40,11 @@ steps: | |||
| matrix: | |||
| - default | |||
| - fleet | |||
| - fleet-endpoint-security | |||
There was a problem hiding this comment.
The ordering in these matrix lists looks arbitrary. Is there a reason for the ordering, or should we have them sorted alphabetically?
There was a problem hiding this comment.
Honestly, there are no ordering rules. Just placed fleet groups together
There was a problem hiding this comment.
Are you going to sort them? If the order doesn't matter, I think it'd be a better user experience when engineers are scrolling through the results of a BK job to have them alphabetical. Plus it would make these lists more easily maintainable (until we figure out making the groups/matrix dynamic).
|
|
I think this PR is now blocked until the issue listed here is understood? https://github.com/elastic/ingest-dev/issues/4216#issuecomment-2554151178 |
pazone
changed the title
|
Blocked by this issue: https://github.com/elastic/ingest-dev/issues/4610 |
What does this PR do?
Extracts 3 new test groups that are executed separately:
Now the longest running group is
fleet-endpoint-security(42 minutes)The
TestRepeatedInstallUninstallon PRs will have 50 iterations instead of 100. For the main and release branches the iterations number will stay 100.Why is it important?
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself