Forward repository proxies to nested smoke test builds

[AlexeyKuznetsov-DD]

What Does This Do

Makes every NestedGradleBuild inherit the outer build's mavenRepositoryProxy and gradlePluginProxy settings.

When an effective proxy is configured, the task:

• forwards it to the nested build as a -P property;
• preserves a value explicitly configured in gradleProperties;
• injects proxy-repositories.init.gradle.kts exactly once, so nested builds do not need custom repository handling;
• tracks the effective proxy as a task input, so proxy changes invalidate cached task output.

Proxy resolution now lives entirely in NestedGradleBuild. The previous CI-only forwarding in SmokeTestAppExtension was removed so manual and extension-created tasks use the same behavior and explicit task overrides work consistently.

Motivation

Nested smoke-test builds use a temporary Gradle user home, so they cannot see proxy settings from the outer build's gradle.properties.

Previously, proxy forwarding lived in CI-only SmokeTestAppExtension conventions. Local builds therefore bypassed configured proxies, while the WildFly earBuild tasks registered directly as NestedGradleBuild tasks did not receive the extension forwarding even on CI.

This caused nested dependency resolution to fall back to Maven Central and fail in environments where direct access is blocked. Centralizing the behavior in the task also ensures future nested builds inherit proxy configuration automatically.

Additional Notes

Verification

• SmokeTestAppPluginTest: 12 passed.
• Four focused SmokeTestAppEndToEndTest proxy regressions passed under JDK 21, covering:
  • local proxy forwarding and exactly one injected init script;
  • a proxy declared only through gradleProperties;
  • an explicit task proxy overriding the outer proxy on CI;
  • cache invalidation when the effective proxy changes.
• ./gradlew spotlessCheck passed.

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

🤖 Generated with Codex.

[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.04 s	14.03 s	[-0.6%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.91 s	13.02 s	[-1.7%; +0.1%] (no difference)
startup:petclinic:appsec:Agent	17.06 s	17.01 s	[-0.6%; +1.2%] (no difference)
startup:petclinic:iast:Agent	17.05 s	17.06 s	[-0.6%; +0.6%] (no difference)
startup:petclinic:profiling:Agent	16.79 s	17.06 s	[-2.5%; -0.6%] (maybe better)
startup:petclinic:sca:Agent	16.72 s	16.57 s	[-0.1%; +1.9%] (no difference)
startup:petclinic:tracing:Agent	16.21 s	16.08 s	[-0.2%; +1.7%] (no difference)

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

[datadog-official]

More details

Proxy precedence, explicit nested property preservation, one-time init-script injection, and cache invalidation all remain consistent with the intended nested-build behavior. Focused plugin tests pass; the end-to-end scenarios could not complete because the sandbox cannot download Gradle 8.14.5, so that environment limitation is the remaining validation gap.

Was this helpful? React 👍 or 👎

_{📊 Validated against 27 scenarios · Open Bits AI session}

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