Upgrade Gradle to 9.8.0

[bric3]

What Does This Do

• Upgrade the Gradle wrapper from 9.7.1 to 9.8.0
• Update the GitLab CI Gradle version used for cache paths.
• Gradle 9.8 highlights: Java 27 daemon and toolchain support, opt-in reuse of Maven mirror settings (unsure it can properly cover all our use cases in the pipeline), clearer problem reports, and up-to-date checks for Maven Publish.

Motivation

Keep the build on the current Gradle release. See the Gradle 9.8.0 release notes.

Additional Notes

The POM change is needed because 9.8.0 now snapshots the POM task’s inputs before, by moving metadata onto the publication preserves the output and avoids writing a finalized property.
See Gradle's 9.8.0's release note on Up-to-date checks for POM generation in Maven publishing

It appears that buildSrc/ and test-published-dependencies/ are not properly configured to use our mirror/proxy, and it appears that when upgrading to Gradle 9.8.0, fetching new required dependencies hit Maven Central and as such got a 429 status to rate limit. This PR applies the same trick that was already applied on build-logic/, but I made them to use gradle properties access, rather that reading seting's ExtraProperties.

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 (not applicable)
• Update public documentation with any new configuration flags or behaviors (not applicable)
• Once approved, use merge queue to merge the PR

[datadog-official]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.16% (-0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: fe4de14 | 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.93 s	13.86 s	[-0.1%; +1.2%] (no difference)
startup:insecure-bank:tracing:Agent	13.02 s	13.04 s	[-0.8%; +0.6%] (no difference)
startup:petclinic:appsec:Agent	17.04 s	16.99 s	[-0.6%; +1.1%] (no difference)
startup:petclinic:iast:Agent	16.93 s	16.97 s	[-1.1%; +0.7%] (no difference)
startup:petclinic:profiling:Agent	16.76 s	16.87 s	[-1.8%; +0.5%] (no difference)
startup:petclinic:sca:Agent	16.97 s	16.81 s	[+0.0%; +1.8%] (maybe worse)
startup:petclinic:tracing:Agent	15.67 s	16.23 s	[-7.5%; +0.6%] (no difference)

Commit: fe4de14e · 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-25T15:43:19.470794Z	fe4de14	Draft marked ready
🔒 Security Review	✅ Completed 2026-09-25T15:45:31.482703Z	fe4de14	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.

[AlexeyKuznetsov-DD]

Cool

[datadog-official]

More details

Proxy properties are consistently resolved through Gradle providers while preserving repository fallbacks, and Maven POM metadata moves onto each publication without changing its values. Targeted Gradle execution could not complete because external artifact repositories were unavailable.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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