-
Notifications
You must be signed in to change notification settings - Fork 725
bk: update junit-annotate to run faster #3015
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
base: main
Are you sure you want to change the base?
Conversation
@v1v 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
@copilot finish the PR, it's still marked as WIP in the description |
Co-authored-by: v1v <[email protected]>
buildkite test it |
Updates the Buildkite pipeline configuration to use a faster container-based approach for the junit-annotate step instead of relying on the GCP provider.
Changes Made
Updated the
:junit: Test results
step in.buildkite/pipeline.yml
to:docker.elastic.co/ci-agent-images/buildkite-junit-annotate:1.0
instead of the GCP providerrun-in-docker: false
configuration to the junit-annotate pluginThis change improves the performance of the junit annotation step by using a dedicated container image instead of relying on the GCP provider to spin up Docker containers.
Fixes #3014.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.