Skip to content

RUM-15510: Resolve dependencies through Magic Mirror Depot in CI#3452

Merged
hamorillo merged 1 commit into
developfrom
hector.morilloprieto/RUM-15510-v2
May 18, 2026
Merged

RUM-15510: Resolve dependencies through Magic Mirror Depot in CI#3452
hamorillo merged 1 commit into
developfrom
hector.morilloprieto/RUM-15510-v2

Conversation

@hamorillo

@hamorillo hamorillo commented May 18, 2026

Copy link
Copy Markdown
Contributor

What and why

Routes Gradle dependency and plugin resolution through Datadog's internal Magic Mirror Depot (depot-read-api-java) when running in GitLab CI, to eliminate HTTP 429 rate-limits from public registries (Maven Central, Gradle Plugin Portal).

The change is gated behind two Gradle properties (mavenRepositoryProxy, gradlePluginProxy) that are only set in CI via .gitlab-ci.yml. Local builds with no properties set are a strict no-op; the existing public registries (mavenCentral, gradlePluginPortal, google, jitpack) remain as fallbacks in every repositories { } block.

Follows the same approach as DataDog/dd-trace-java#9351 and DataDog/dd-trace-java#9802 (which switched property injection from gradle.properties file writes to ORG_GRADLE_PROJECT_* environment variables).

What changes

CI configuration

  • .gitlab-ci.yml: declare MAVEN_REPOSITORY_PROXY and GRADLE_PLUGIN_PROXY env vars pointing at the depot URL.
  • ci/pipelines/default-pipeline.yml: add a default.before_script that exports ORG_GRADLE_PROJECT_mavenRepositoryProxy and ORG_GRADLE_PROJECT_gradlePluginProxy. Gradle reads any ORG_GRADLE_PROJECT_<name> env var as providers.gradleProperty("<name>"), and the env vars naturally inherit to child Gradle processes via the shell environment.

How to verify

  1. No-op locally: build without the proxy properties (the normal developer flow) — no behavior change. Confirmed via ./gradlew :features:dd-sdk-android-session-replay-compose:assembleRelease with cold cache; resolves entirely from public registries.
  2. Depot routing in CI: on the CI runner the proxy properties are set; every Gradle process reads them via providers.gradleProperty(...). Verified via a temporary --info diagnostic on the test:tools job that logged all repository URL hits (logs here) — depot served Maven Central artifacts, Google and Jitpack served their canonical content, no direct repo1.maven.org or repo.maven.apache.org traffic.
  3. Existing test suites pass: full CI pipeline green on hector.morilloprieto/RUM-15510-v2.

@hamorillo

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 448cdf631a

ℹ️ 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".

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

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread ci/pipelines/default-pipeline.yml Outdated
Routes Gradle dependency and plugin resolution through Datadog's internal Magic Mirror Depot (depot-read-api-java) when running in GitLab CI, to eliminate HTTP 429 rate-limits from public registries.

The change is gated behind two Gradle properties (mavenRepositoryProxy, gradlePluginProxy) that are only set in CI via .gitlab-ci.yml. Local builds with no property set are a strict no-op; the existing public registries (mavenCentral, gradlePluginPortal, google, jitpack) remain as fallbacks in every repositories block.

Follows the same approach as DataDog/dd-trace-java#9351, targeting the Magic Mirror Depot URL directly.
@hamorillo
hamorillo force-pushed the hector.morilloprieto/RUM-15510-v2 branch from 448cdf6 to 13bffbc Compare May 18, 2026 06:29
@hamorillo

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🎉

ℹ️ 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".

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

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@codecov-commenter

codecov-commenter commented May 18, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.07%. Comparing base (38daa7d) to head (13bffbc).
⚠️ Report is 29 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3452      +/-   ##
===========================================
+ Coverage    72.05%   72.07%   +0.02%     
===========================================
  Files          961      961              
  Lines        35399    35398       -1     
  Branches      5882     5882              
===========================================
+ Hits         25506    25511       +5     
- Misses        8274     8276       +2     
+ Partials      1619     1611       -8     

see 42 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@hamorillo
hamorillo marked this pull request as ready for review May 18, 2026 08:47
@hamorillo
hamorillo requested review from a team as code owners May 18, 2026 08:47

@0xnm 0xnm left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@aleksandr-gringauz aleksandr-gringauz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@hamorillo
hamorillo merged commit 873b529 into develop May 18, 2026
27 checks passed
@hamorillo
hamorillo deleted the hector.morilloprieto/RUM-15510-v2 branch May 18, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants