[AlexeyKuznetsov-DD]

What Does This Do

Attaches the modifiable-config test agent to test JVMs that also run the JaCoCo coverage agent.

Motivation

The plugin skips attaching when another -javaagent is already present, and it counted JaCoCo as one. So modules with coverage enabled never got the agent, and Config / InstrumenterConfig stayed unmodifiable at load time. Spock modules hid this because ConfigTransformSpockExtension rewrites Config at runtime. Modules with no Spock, such as internal-api once its Groovy is removed, fail with "Config/InstrumenterConfig INSTANCE fields are not modifiable".

Additional Notes

This affects every module's tests, so it is a separate PR. :communication:test (Spock + JUnit, 297 tests) passes with both agents attached.

#13152 (Groovy cleanup for internal-api) is stacked on this one.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

🤖 Generated with Claude Code

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.01 s	13.99 s	[-0.6%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.91 s	12.92 s	[-0.7%; +0.5%] (no difference)
startup:petclinic:appsec:Agent	17.88 s	17.70 s	[+0.2%; +1.9%] (maybe worse)
startup:petclinic:iast:Agent	17.55 s	17.78 s	[-2.2%; -0.4%] (maybe better)
startup:petclinic:profiling:Agent	17.67 s	17.57 s	[-0.6%; +1.8%] (no difference)
startup:petclinic:sca:Agent	17.77 s	17.59 s	[+0.1%; +1.9%] (maybe worse)
startup:petclinic:tracing:Agent	16.77 s	16.80 s	[-1.2%; +0.9%] (no difference)

Commit: 852015fe · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-02T18:06:40.026519Z	852015f	Draft marked ready
🔒 Security Review	✅ Completed 2026-11-02T18:05:51.842610Z	852015f	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-prod-us1-4]

More details

The JaCoCo exemption matches the coverage agent used by this build and preserves the skip behavior when another Java agent is present.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 852015f}

[AlexeyKuznetsov-DD]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-11-02 18:41:52 UTC ℹ️ Start processing command /merge

---

2026-11-02 18:41:56 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-11-02 19:41:07 UTC ℹ️ MergeQueue: This merge request was merged