Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Sep 19, 2025

Updated the Buildkite junit-annotate configuration to use faster container-based execution instead of the GCP provider.

Changes Made

  • Plugin Version: Upgraded junit-annotate from v2.4.1 to v2.7.0
  • Agent Configuration: Replaced provider: "gcp" with image: "docker.elastic.co/ci-agent-images/buildkite-junit-annotate:1.0"
  • Execution Mode: Added run-in-docker: false to the plugin configuration
  • Preserved Settings: Maintained existing artifacts: "junit-*.xml" and fail-build-on-error: true configurations

The updated configuration follows the pattern specified in the issue, replacing the GCP provider-based setup with a dedicated container image that provides faster execution while maintaining all existing functionality.

Before

- label: ":junit: Junit annotate"
  plugins:
    - junit-annotate#v2.4.1:
        artifacts: "junit-*.xml"
        fail-build-on-error: true
  agents:
    provider: "gcp" #junit plugin requires docker

After

- label: ":junit: Junit annotate"
  agents:
    # requires at least "bash", "curl" and "git"
    image: "docker.elastic.co/ci-agent-images/buildkite-junit-annotate:1.0"
  plugins:
    - junit-annotate#v2.7.0:
        artifacts: "junit-*.xml"
        fail-build-on-error: true
        run-in-docker: false

Fixes #218.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI assigned Copilot and v1v Sep 19, 2025
Copy link
Contributor Author

Copilot AI commented Sep 19, 2025

@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.

@v1v
Copy link
Member

v1v commented Sep 19, 2025

@copilot finish the PR, it's still marked as WIP in the description

Copy link
Contributor Author

Copilot AI commented Sep 19, 2025

@copilot finish the PR, it's still marked as WIP in the description

Done! The PR is now complete. I've updated the junit-annotate configuration in .buildkite/pipeline.yml to use the faster container setup as requested in the issue. The changes include:

  • Upgraded junit-annotate from v2.4.1 to v2.7.0
  • Replaced provider: "gcp" with image: "docker.elastic.co/ci-agent-images/buildkite-junit-annotate:1.0"
  • Added run-in-docker: false configuration
  • Preserved existing settings for artifacts and fail-build-on-error

The PR is ready for review and no longer WIP. (6e699b1)

Copilot AI changed the title [WIP] bk: update unit-annotate to run faster bk: update junit-annotate to run faster Sep 19, 2025
@v1v
Copy link
Member

v1v commented Sep 22, 2025

buildkite test it

@v1v v1v marked this pull request as ready for review September 22, 2025 10:50
@v1v v1v requested review from a team September 22, 2025 10:50
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @v1v @Copilot

Copy link

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n merged commit 6faa1b8 into main Sep 22, 2025
15 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bk: update unit-annotate to run faster

4 participants