Use Fabric DNS endpoint for MASS pull-through cache

[AlexeyKuznetsov-DD]

What Does This Do

Points MASS_READ_URL in .gitlab-ci.yml at the Fabric DNS endpoint (mass-read.rapid-dependency-management-mass.all-clusters.local-dc.fabric.dog:8443) instead of the Fabric ISP URL (mass-read.us1.ddbuild.io).

MASS_READ_URL is the single source of truth — the Gradle wrapper distributionUrl rewrite, the MassExtension.artifactUrl(...) helper, and the smoke-test Gradle distribution resolution all read it — so this one-line change covers every MASS consumer.

Motivation

CI jobs were intermittently failing to download the Gradle distribution with:

java.io.IOException: Server returned HTTP response code: 503 for URL:
https://mass-read.us1.ddbuild.io/internal/artifact/services.gradle.org/distributions/gradle-8.14.5-bin.zip

Per the MASS team, these 503s are transient failures in the Fabric ISP layer (no 5XX on the service side). They recommend migrating from the ISP URL to the Fabric DNS endpoint for more consistent availability.

Additional Notes

• MAVEN_REPOSITORY_PROXY / GRADLE_PLUGIN_PROXY (depot-read-api-java.us1.ddbuild.io) are a different service and left unchanged.
• Worth confirming GitLab runners can resolve the internal .fabric.dog:8443 DNS endpoint.

🤖 Generated with Claude Code