-
Notifications
You must be signed in to change notification settings - Fork 204
[ci] migrate extended runtime leak tests to buildkite #7931
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci] migrate extended runtime leak tests to buildkite #7931
Conversation
3d63b2b to
6b2bf11
Compare
|
💚 Build Succeeded
|
v1v
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I think we are reaching a point where we copy&paste groups/steps is becoming a burden. I'll start a conversation internally about tit
I agree 100% with this and I will be happy to join any discussions about it 🙂 |
|
I will kindly also request a review from you @ycombinator (a control-plane team member) just to have an extra pair of 👀 here from the product PoV 🙏 |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
6b2bf11 to
4e1a561
Compare
|
dliappis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thank you!
pazone
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
The TEST_NAME_PATTERN reminds me that we are about to reach the maintainability threshold. Let's consider a follow-up simplification and refactoring
pchila
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@Mergifyio backport 8.17 8.18 8.19 9.0 |
✅ Backports have been created
|
(cherry picked from commit f108618) # Conflicts: # .buildkite/scripts/buildkite-integration-tests.sh # .buildkite/scripts/integration-tests.ps1
(cherry picked from commit f108618)
(cherry picked from commit f108618)
(cherry picked from commit f108618)
…uildkite (#8307) * ci: migrate extended runtime leak tests to buildkite (#7931) (cherry picked from commit f108618) # Conflicts: # .buildkite/scripts/buildkite-integration-tests.sh # .buildkite/scripts/integration-tests.ps1 * fix: resolve conflicts * fix: remove --junitfile-hide-skipped-tests from gotestsum --------- Co-authored-by: Panos Koutsovasilis <panos.koutsovasilis@elastic.co>





What does this PR do?
This PR migrates the Extended Runtime Leak Tests to Buildkite, where all other integration and Kubernetes tests now reside. The new setup runs these tests on Windows 2022, Windows 2025, and Ubuntu 24.04 using existing prebuilt VM images. The old step is removed to avoid duplication and eliminate the dependency on OGC.
Proof that we run the same tests:
Why is it important?
This resolves reliability issues in the old extended testing setup, aligning them with our current CI strategy and infrastructure.
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
None. This change only affects internal CI configuration.
How to test this PR locally
Open a PR 🙂
Related issues