Make dd-trace-java.test-jvm-constraints reports additional JVM data in test task inputs

[bric3]

What Does This Do

Include the selected test JVM's vendor, full runtime version and VM version in task inputs through testJvmConstraints. The inputs follow each task's final javaLauncher, including defaults and overrides.

Motivation

Changing a JVM patch/build or vendor can currently reuse test results from the same Java major version. This makes those changes invalidate both up-to-date checks and build-cache entries.

Related to the S3 build cache in #12604.

Additional Notes

Regression tests vary each metadata field while keeping the executable and Java major version fixed, and check both up-to-date and build-cache reuse. Identity uses reported JVM metadata rather than hashes of JDK binaries.

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

[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	13.98 s	13.97 s	[-0.8%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	12.97 s	[-0.9%; +0.6%] (no difference)
startup:petclinic:appsec:Agent	16.98 s	16.89 s	[-0.5%; +1.5%] (no difference)
startup:petclinic:iast:Agent	16.88 s	16.36 s	[-1.3%; +7.7%] (no difference)
startup:petclinic:profiling:Agent	16.66 s	16.72 s	[-1.5%; +0.7%] (no difference)
startup:petclinic:sca:Agent	16.92 s	16.92 s	[-0.9%; +0.9%] (no difference)
startup:petclinic:tracing:Agent	16.16 s	16.17 s	[-1.0%; +0.9%] (no difference)

Commit: 95abc7b9 · 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-09-24T15:34:46.707734Z	95abc7b	Draft marked ready
🔒 Security Review	✅ Completed 2026-09-24T15:32:55.335139Z	95abc7b	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.

[sarahchen6]

Nice

[bric3]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-24 15:43:23 UTC ℹ️ Start processing command /merge

---

2026-09-24 15:43:27 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-09-24 16:46:20 UTC ℹ️ MergeQueue: This merge request was merged

[datadog-datadog-prod-us1]

More details

Each test task uses its final Java launcher data. A vendor or full JVM version change now invalidates the task cache.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 95abc7b · @DataDog review to ask questions}