-
Notifications
You must be signed in to change notification settings - Fork 204
bk: update junit-annotate to run faster #10064
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
Conversation
|
This pull request does not have a backport label. Could you fix it @Copilot? 🙏
|
|
@copilot this PR is WIP, finish the remaining work |
Co-authored-by: v1v <[email protected]>
Completed the remaining work to update junit-annotate configuration. Updated |
fr4nc1sc0-r4m0n
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
|
buildkite test this |
|
💛 Build succeeded, but was flaky
Failed CI Stepscc @v1v @Copilot |
(cherry picked from commit bfaf781)
(cherry picked from commit bfaf781)
(cherry picked from commit bfaf781)





Updates the Buildkite junit-annotate plugin configuration to run faster using containers instead of the GCP provider.
Changes Made
junit-annotate#v2.5.0tojunit-annotate#v2.7.0docker.elastic.co/ci-agent-images/buildkite-junit-annotate:1.0run-in-docker: falsefor improved execution speedThe configuration change in
.buildkite/pipeline.ymltransforms the junit annotation step from:To:
This change maintains all existing functionality while providing faster execution by using a dedicated container image instead of provisioning GCP instances.
Fixes #10063.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.