[bric3]

What Does This Do

Add dd-openfeature to the reference and failure artifacts in validate_build, then enable its compareToReferenceJar task.

Motivation

The build job already produces the jar, but validate_build does not preserve a reference copy.

Follow-up to

• Publish dd-openfeature in PR snapshots #12400, which added the build artifact,
• and [APMLP-1509] Catch build issue by comparing release artifacts with jardiff after build job #11959, which added the comparison job.

Additional Notes

The focused jar comparison passed locally using a copied reference jar.

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

[datadog-prod-us1-6]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.86% (+0.01%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 7befb5e | Docs | Give us feedback!}

[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.99 s	13.89 s	[-0.0%; +1.6%] (no difference)
startup:insecure-bank:tracing:Agent	12.91 s	12.94 s	[-1.0%; +0.4%] (no difference)
startup:petclinic:appsec:Agent	17.16 s	16.42 s	[+0.3%; +8.7%] (maybe worse)
startup:petclinic:iast:Agent	17.01 s	17.02 s	[-0.9%; +0.7%] (no difference)
startup:petclinic:profiling:Agent	16.75 s	16.96 s	[-2.5%; +0.1%] (no difference)
startup:petclinic:sca:Agent	17.09 s	16.89 s	[+0.3%; +2.0%] (maybe worse)
startup:petclinic:tracing:Agent	15.85 s	16.13 s	[-5.9%; +2.4%] (no difference)

Commit: 7befb5e1 · 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-10-22T11:58:24.741003Z	7befb5e	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-22T12:00:49.041578Z	7befb5e	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.

[PerfectSlayer]

Duplicate of #12844

[datadog-prod-us1-6]

More details

The OpenFeature artifact paths match the JAR already produced by CI, allowing the enabled comparison task to locate its reference. No actionable defects were identified.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 7befb5e}

[bric3]

Closing because duplicate of #12844 as @PerfectSlayer mentionned