Route Gradle distribution through MASS pull-through cache

[jzh0u]

Summary

• Routes Gradle wrapper distribution downloads through the MASS pull-through cache (mass-read.us1.ddbuild.io) instead of directly hitting services.gradle.org
• Adds MASS_READ_URL CI variable pointing to the prod MASS read endpoint
• Fixes GRADLE_VERSION to match the version in gradle/wrapper/gradle-wrapper.properties (8.14.5)
• On cache miss, MASS returns the upstream URL immediately and fills the cache in the background; subsequent requests serve from S3

How it works

A sed in before_script rewrites gradle-wrapper.properties at CI time:

distributionUrl=https\://services.gradle.org/distributions/...
→
distributionUrl=https\://mass-read.us1.ddbuild.io/internal/artifact/services.gradle.org/distributions/...

MASS pull-through is already enabled in prod (mass-pullthrough-enabled feature flag). The services.gradle.org domain is already in the MASS egress allowlist.

Test plan

• Verify CI pipeline passes with the rewritten distributionUrl
• Confirm second CI run hits S3 cache (HTTP 307 → S3 presigned URL) rather than upstream

Part of DPCYMGMT-3608.

🤖 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

Startup Time

Scenario	This PR	master	Change
insecure-bank / iast	14,005 ms	13,940 ms	+0.5%
insecure-bank / tracing	12,929 ms	12,967 ms	-0.3%
petclinic / appsec	16,512 ms	15,504 ms	+6.5%
petclinic / iast	16,429 ms	15,797 ms	+4.0%
petclinic / profiling	16,236 ms	16,361 ms	-0.8%
petclinic / tracing	15,824 ms	15,981 ms	-1.0%

Commit: 43a86682 · 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.

[AlexeyKuznetsov-DD]

LGTM, I can see on CI in logs:

Downloading https://mass-read.us1.ddbuild.io/internal/artifact/services.gradle.org/distributions/gradle-8.14.5-bin.zip
.............10%.............20%.............30%.............40%.............50%.............60%..............70%.............80%.............90%.............100%

But let's get review from @bric3 too.

[dd-octo-sts]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 558c98298f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[bric3]

Pre-approving, but Gitlab is probably "hydrating" gradle from a cache. I believe this might prevent gradle wrapper from fetching from MASS. I didn't look at the commit history so bear with me if I missed something, otherwise I'd say that in order to test this properly there could be a commit adding a line that deletes .gradle before the main job script executes. Then remove that change before adding the PR to the merge queue.

[bric3]

praise: Ouch, good find.

[AlexeyKuznetsov-DD]

Pre-approving, but Gitlab is probably "hydrating" gradle from a cache. I believe this might prevent gradle wrapper from fetching from MASS. I didn't look at the commit history so bear with me if I missed something, otherwise I'd say that in order to test this properly there could be a commit adding a line that deletes .gradle before the main job script executes. Then remove that change before adding the PR to the merge queue.

@bric3 AFAIK nightly populate caches jobs runs from scratch -> no-caches, so it will be cached by MASS.
Also we have tests that loads old Gradle distros, I hope they will benefit a lot.

[bric3]

@AlexeyKuznetsov-DD Yeah I meant only for this PR.

[AlexeyKuznetsov-DD]

/merge --commit-message "Route Gradle distribution through MASS pull-through cache"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-05-27 16:34:00 UTC ℹ️ Start processing command /merge --commit-message "Route Gradle distribution through MASS pull-through cache"

---

2026-05-27 16:34:05 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-05-27 17:44:12 UTC ℹ️ MergeQueue: This merge request was merged

[jzh0u]

@AlexeyKuznetsov-DD Thanks for fixing and merging