Route Robolectric downloads through repository proxy

[AlexeyKuznetsov-DD]

What Does This Do

Routes Robolectric runtime Android SDK downloads through the configured Maven repository proxy.

Motivation

Robolectric resolves SDK artifacts outside the Gradle dependency resolver, so it did not inherit the existing proxy configuration. Passing the proxy explicitly avoids direct runtime downloads from public Maven Central.

Additional Notes

The failure occurred while Robolectric was fetching its Android SDK artifact at test runtime:

AndroidJUnit4RunnerTest > classMethod FAILED
    java.lang.AssertionError at MavenArtifactFetcher.java:129
        Caused by: java.util.concurrent.ExecutionException at AbstractFuture.java:292
            Caused by: java.io.IOException at HttpURLConnection.java:2052

MavenArtifactFetcher.java:129 is the Robolectric artifact-download failure path. The nested HttpURLConnection → IOException shows that the runtime fetch failed before the test assertion ran. A later retry passed, which is consistent with a transient download failure.

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

Jira ticket: N/A

[cit-pr-commenter-54b7da]

Test Environment - sbt-scalatest

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	55.28	54.33	$\color{red}{\blacktriangle}$ +0.95	55.43	$\color{green}{\blacktriangledown}$ -0.15	42/230
agentEvpProxy	55.57	n/a	n/a	n/a	n/a	-

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[cit-pr-commenter-54b7da]

Test Environment - heliboard

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	-39.42	9.54	$\color{green}{\blacktriangledown}$ -48.96	9.73	$\color{green}{\blacktriangledown}$ -49.15	19/112

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[cit-pr-commenter-54b7da]

Test Environment - nebula-release-plugin

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	36.51	37.15	$\color{green}{\blacktriangledown}$ -0.64	37.15	$\color{green}{\blacktriangledown}$ -0.64	23/133
agentless	36.28	36.42	$\color{green}{\blacktriangledown}$ -0.14	36.42	$\color{green}{\blacktriangledown}$ -0.14	23/114
agentlessCodeCoverage	44.49	44.48	$\color{red}{\blacktriangle}$ +0.01	44.48	$\color{red}{\blacktriangle}$ +0.01	23/113
agentlessLineCoverage	55.34	56.55	$\color{green}{\blacktriangledown}$ -1.21	56.55	$\color{green}{\blacktriangledown}$ -1.21	23/116

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[cit-pr-commenter-54b7da]

Test Environment - netflix-zuul

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	87.13	87.80	$\color{green}{\blacktriangledown}$ -0.67	87.80	$\color{green}{\blacktriangledown}$ -0.67	25/149
agentless	80.48	81.05	$\color{green}{\blacktriangledown}$ -0.57	81.05	$\color{green}{\blacktriangledown}$ -0.57	25/122
agentlessCodeCoverage	95.75	95.12	$\color{red}{\blacktriangle}$ +0.63	97.04	$\color{green}{\blacktriangledown}$ -1.29	24/120
agentlessLineCoverage	111.30	111.62	$\color{green}{\blacktriangledown}$ -0.32	111.62	$\color{green}{\blacktriangledown}$ -0.32	23/119

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[cit-pr-commenter-54b7da]

Test Environment - reactive-streams-jvm

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	14.24	21.65	$\color{green}{\blacktriangledown}$ -7.41	21.65	$\color{green}{\blacktriangledown}$ -7.41	22/150
agentless	11.62	18.82	$\color{green}{\blacktriangledown}$ -7.20	18.82	$\color{green}{\blacktriangledown}$ -7.20	20/117
agentlessCodeCoverage	12.98	19.99	$\color{green}{\blacktriangledown}$ -7.01	19.99	$\color{green}{\blacktriangledown}$ -7.01	20/114
agentlessLineCoverage	18.56	26.45	$\color{green}{\blacktriangledown}$ -7.89	26.98	$\color{green}{\blacktriangledown}$ -8.42	18/108

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[cit-pr-commenter-54b7da]

Test Environment - okhttp

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	15.66	19.59	$\color{green}{\blacktriangledown}$ -3.93	19.59	$\color{green}{\blacktriangledown}$ -3.93	25/147
agentless	14.53	19.20	$\color{green}{\blacktriangledown}$ -4.67	19.20	$\color{green}{\blacktriangledown}$ -4.67	22/117
agentlessCodeCoverage	17.76	22.54	$\color{green}{\blacktriangledown}$ -4.78	22.54	$\color{green}{\blacktriangledown}$ -4.78	22/119
agentlessLineCoverage	34.20	38.67	$\color{green}{\blacktriangledown}$ -4.47	39.45	$\color{green}{\blacktriangledown}$ -5.25	21/118

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[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	14.84 s	14.68 s	[+0.1%; +2.1%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.57 s	13.76 s	[-2.3%; -0.5%] (maybe better)
startup:petclinic:appsec:Agent	16.91 s	16.80 s	[-0.3%; +1.6%] (no difference)
startup:petclinic:iast:Agent	16.87 s	16.89 s	[-0.8%; +0.6%] (no difference)
startup:petclinic:profiling:Agent	16.57 s	16.72 s	[-1.9%; +0.1%] (no difference)
startup:petclinic:sca:Agent	16.78 s	16.62 s	[+0.1%; +1.9%] (maybe worse)
startup:petclinic:tracing:Agent	16.05 s	15.63 s	[-1.7%; +7.1%] (no difference)

Commit: 28c95d98 · 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.

[cit-pr-commenter-54b7da]

Test Environment - sonar-kotlin

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	6.09	12.62	$\color{green}{\blacktriangledown}$ -6.53	12.87	$\color{green}{\blacktriangledown}$ -6.78	21/138
agentless	5.00	12.12	$\color{green}{\blacktriangledown}$ -7.12	12.12	$\color{green}{\blacktriangledown}$ -7.12	21/111
agentlessCodeCoverage	8.15	15.11	$\color{green}{\blacktriangledown}$ -6.96	15.11	$\color{green}{\blacktriangledown}$ -6.96	21/111
agentlessLineCoverage	11.79	17.03	$\color{green}{\blacktriangledown}$ -5.24	17.38	$\color{green}{\blacktriangledown}$ -5.59	20/111

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[cit-pr-commenter-54b7da]

Test Environment - spring_boot

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	18.45	16.36	$\color{red}{\blacktriangle}$ +2.09	16.36	$\color{red}{\blacktriangle}$ +2.09	21/145
agentless	9.78	9.73	$\color{red}{\blacktriangle}$ +0.05	9.73	$\color{red}{\blacktriangle}$ +0.05	21/117
agentlessCodeCoverage	14.17	13.40	$\color{red}{\blacktriangle}$ +0.77	13.40	$\color{red}{\blacktriangle}$ +0.77	21/117
agentlessLineCoverage	22.51	22.09	$\color{red}{\blacktriangle}$ +0.42	22.54	$\color{green}{\blacktriangledown}$ -0.03	21/118

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[datadog-datadog-prod-us1-2]

More details

The same nonblank MAVEN_REPOSITORY_PROXY value already used by the fixture’s Gradle repositories is passed to Robolectric’s test JVM, while an absent or blank value leaves Robolectric’s default repository behavior untouched.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 28c95d9 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[cit-pr-commenter-54b7da]

Test Environment - sonar-java

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	52.80	7.21	$\color{red}{\blacktriangle}$ +45.59	11.19	$\color{red}{\blacktriangle}$ +41.61	22/141
agentless	48.10	4.28	$\color{red}{\blacktriangle}$ +43.82	13.94	$\color{red}{\blacktriangle}$ +34.16	21/114
agentlessCodeCoverage	92.19	79.45	$\color{red}{\blacktriangle}$ +12.74	82.69	$\color{red}{\blacktriangle}$ +9.50	21/114
agentlessLineCoverage	135.23	111.62	$\color{red}{\blacktriangle}$ +23.61	125.85	$\color{red}{\blacktriangle}$ +9.38	20/113

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[cit-pr-commenter-54b7da]

Test Environment - pass4s

Job Status: 🟢 success

Scenario	This PR (%)	7d median	Δ 7d	30d median	Δ 30d	runs (7d/30d)
agent	9.55	9.54	$\color{red}{\blacktriangle}$ +0.01	9.54	$\color{red}{\blacktriangle}$ +0.01	20/113
agentless	12.14	10.33	$\color{red}{\blacktriangle}$ +1.81	9.16	$\color{red}{\blacktriangle}$ +2.98	20/113
agentlessCodeCoverage	11.62	17.03	$\color{green}{\blacktriangledown}$ -5.41	16.36	$\color{green}{\blacktriangledown}$ -4.74	19/110

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

[AlexeyKuznetsov-DD]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-14 16:34:56 UTC ℹ️ Start processing command /merge

---

2026-08-14 16:35:01 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-14 17:08:45 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 39ac5c7:

• test_inst: [tip, 1/8]
• test_inst: [zulu11, 3/8]
• test_inst: [17, 3/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[AlexeyKuznetsov-DD]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-14 17:52:06 UTC ℹ️ Start processing command /merge

---

2026-08-14 17:52:10 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-14 18:24:15 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for d7ede30:

• test_inst: [ibm8, 1/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[AlexeyKuznetsov-DD]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-14 19:21:44 UTC ℹ️ Start processing command /merge

---

2026-08-14 19:21:50 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-14 20:00:20 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 044f2dd:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.