Run BK integration tests on PRs and release branches #6148
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pazone
added
enhancement
pazone
force-pushed
the
ci_bk_it_cutover
branch
from
defb1e4
to
7aec494
Compare
blakerouse
requested changes
Nov 27, 2024
|
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
rdner
reviewed
Nov 28, 2024
|
|
||
| When creating a new test group, it is important to add the new group to the job in the `.buildkite/bk.integration.pipeline.yml` file. This will ensure that the new group is executed in the CI pipeline. | ||
|
|
||
| Add the new group to the `matrix` in the corresponding steps. The matrix is a list of all the test groups that are executed in the teh step. |
There was a problem hiding this comment.
Not sure I understood the sentence though.
Suggested change
| Add the new group to the `matrix` in the corresponding steps. The matrix is a list of all the test groups that are executed in the teh step. | |
| Add the new group to the `matrix` in the corresponding steps. The matrix is a list of all test groups that are executed in the step. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Runs the new integration testing infrastructure provisioned by buildkite and terraform (ESS)
Integration tests take 1 h 10 minutes instead of ~1:30.
Independent test groups execution allows to retry tests independently with a dedicated ESS stack:
Build example 1
Build example 2
Build example 3
Build example 4
We run the same tests as we run in the OGC integration tests
What groups do we run
What OS do we run
By comparing test reports, I verified that we run the same test sets for groups. Placed the tests in groups in this spreadsheet
Why is it important?
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself