Use configured mirrors for buildSrc tests

[AlexeyKuznetsov-DD]

What Does This Do

Refactors buildSrc test fixtures and Muzzle repository setup to use configured dependency mirrors when present. Without mirror configuration, tests continue to use the standard public repositories. Range-resolution tests use local fixtures where possible.

Motivation

Keep build-logic tests consistent with repository configuration in automated builds while preserving a zero-configuration local workflow for contributors.

Additional Notes

Validation:

• ./gradlew -p buildSrc :test -PrunBuildSrcTests --rerun-tasks without mirror configuration: 291 tests passed
• ./gradlew :buildSrc:test -PrunBuildSrcTests --rerun-tasks with mirror configuration: 291 tests passed
• ./gradlew -p buildSrc spotlessCheck

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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-03T00:56:12.313157Z	7b493be	Draft marked ready

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-datadog-prod-us1-2]

More details

The code keeps public repositories when no proxy exists. It uses the configured mirror when a proxy exists, with no reportable defect.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[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.83 s	14.72 s	[-0.3%; +1.8%] (no difference)
startup:insecure-bank:tracing:Agent	13.56 s	13.61 s	[-1.2%; +0.5%] (no difference)
startup:petclinic:appsec:Agent	17.02 s	17.18 s	[-5.3%; +3.4%] (no difference)
startup:petclinic:iast:Agent	17.45 s	17.64 s	[-1.8%; -0.2%] (maybe better)
startup:petclinic:profiling:Agent	17.57 s	17.32 s	[+0.2%; +2.8%] (maybe worse)
startup:petclinic:sca:Agent	17.61 s	17.54 s	[-0.4%; +1.2%] (no difference)
startup:petclinic:tracing:Agent	16.61 s	16.71 s	[-1.6%; +0.4%] (no difference)

Commit: 7b493be2 · 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]

/gitlab resync-job-status --bypass-required-checks-syncing-strategy

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-03 02:43:46 UTC ℹ️ Start processing command /gitlab resync-job-status --bypass-required-checks-syncing-strategy

---

2026-09-03 02:50:21 UTC ℹ️ Devflow: /gitlab resync-job-status --bypass-required-checks-syncing-strategy

392 jobs status updated and 582 skipped for a total of 974 jobs, 1 pipeline status(es) synced