Reuse Gradle plugin cache across nightly builds

[AlexeyKuznetsov-DD]

What Does This Do

Adds a dedicated pull-push cache for Gradle plugin dependencies during nightly cache population. Dependency-cache population jobs restore this cache, seed their otherwise cold Gradle homes, and continue publishing the existing self-contained dependency caches.

The population jobs also wait for their build-cache producers, making build-cache reuse deterministic.

Motivation

Nightly dependency-cache jobs currently resolve the same Gradle plugins from scratch even though plugin versions change infrequently. Reusing a small persistent plugin cache reduces redundant downloads while keeping project dependency population cold.

Additional Notes

Validation:

• Parsed the GitLab configuration and verified the expanded cache mappings, policies, nightly rules, and job dependencies.
• Ran ./gradlew help -PskipTests with a clean Gradle home.
• Verified that a second clean Gradle home seeded only with the plugin cache can configure the build using ./gradlew help -PskipTests --offline.
• Ran ./gradlew spotlessCheck.

Contributor Checklist

• Format the title according to the contribution guidelines.
• Assign the required type and component labels.
• Avoid issue-linking keywords.
• CODEOWNERS update is not required because no source files were added, migrated, or deleted.
• Public documentation is not required because no public configuration or behavior changed.
• 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-04T16:25:40.011430Z	eda82df	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 new cache jobs use consistent keys, paths, policies, and job links. The dependency jobs copy the plugin cache into each clean Gradle home as intended.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eda82df335

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

[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.72 s	14.65 s	[-0.4%; +1.4%] (no difference)
startup:insecure-bank:tracing:Agent	13.54 s	13.62 s	[-1.3%; +0.1%] (no difference)
startup:petclinic:appsec:Agent	16.96 s	16.98 s	[-1.1%; +0.9%] (no difference)
startup:petclinic:iast:Agent	16.84 s	16.96 s	[-1.6%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	16.71 s	16.82 s	[-1.8%; +0.5%] (no difference)
startup:petclinic:sca:Agent	17.02 s	16.77 s	[+0.4%; +2.6%] (maybe worse)
startup:petclinic:tracing:Agent	16.07 s	16.24 s	[-2.2%; +0.2%] (no difference)

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

/merge -f --reason "Fix for nightly build, no need to run MQ"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-04 21:01:56 UTC ℹ️ Start processing command /merge -f --reason "Fix for nightly build, no need to run MQ"

---

2026-09-04 21:02:00 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-09-04 21:02:10 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: Fix for nightly build, no need to run MQ