[sarahchen6]

What Does This Do

If [ci: *SKIP_BUILD_CACHE*] is in the commit message, then force fresh Gradle task execution. This is ignored in publication stages to avoid publishing separately build artifacts.

Motivation

Fresh Gradle task execution can be useful when diagnosing failures with reused outputs. The GitLab caches still remain available.

Additional Notes

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: https://datadoghq.atlassian.net/browse/APMLP-1897

[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-11-04T18:55:54.972277Z	d06027e	PR opened
🔒 Security Review	✅ Completed 2026-11-04T18:57:34.687610Z	d06027e	PR opened

ℹ️ 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]

More details

Combined directives such as [ci: ARM64, SKIP_BUILD_CACHE] enable fresh Gradle task execution while preserving the existing environment-variable override. The reviewer’s targeted checks covered case sensitivity and nonmatching messages without identifying a defect.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit d06027e}

[bric3]

For the reader: I think this is important to consider SKIP_BUILD_CACHE as a opt-in diagnostic falg. While potentially useful, it has the following behavior that may not be suitable for daily use or release.

• validate_build

  In #12604 this job is a matrix that validates both runs with build cache and without. But having SKIP_BUILD_CACHE make validate_build always run without build cache (whioch can be confusing).

  i.e. the matrix no longer covers cached versus uncached.

• Runtime impact

  Today there's no shared Gradle build cache across pipelines, it's being worked one as part of #12604. What happens today, i.e. before #12604, GitLab passes prepared outputs between jobs within a pipeline using archives keyed by $CI_PIPELINE_ID-$CACHE_TYPE.

  The initial build and build_tests jobs could push to these gitlab cache. But when the S3 Build cache will be enabled, this intra pipeline won't be available either, forcing additional work downstream:

  • Jobs will have to do again compilation, code generation, packaging and other selected build dependencies that would normally reuse previous outputs.
  • The runtime cost depends on each job's usual reuse. Pipeline duration also depends on whether the affected jobs are on the critical path.
  • Note that dependencies and plugin caches remain available, because they are GitLab cache which is untouched by the S3 Build cache changes in #12604.

• Publishing risk

  If a master or release pipeline builds a commit with SKIP_BUILD_CACHE, the deploy_to_maven_central job will then also receives --no-build-cache --rerun-tasks. And its publishToSonatype invocation forces the archive-producing tasks to execute again.

  And unfortunately the validate_build comparison won;t cover properly the files produced by that publication rebuild anymore. In short : if output is non-deterministic, the published artifacts can differ from the compared artifacts.

  Maybe excluding publication from the commit-message could help, or even disabling all publication jobs.

[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	13.96 s	13.81 s	[+0.5%; +1.8%] (maybe worse)
startup:insecure-bank:tracing:Agent	12.92 s	13.00 s	[-1.4%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	17.21 s	17.13 s	[-0.3%; +1.3%] (no difference)
startup:petclinic:iast:Agent	16.97 s	17.04 s	[-1.1%; +0.3%] (no difference)
startup:petclinic:profiling:Agent	16.62 s	16.97 s	[-3.3%; -0.9%] (maybe better)
startup:petclinic:sca:Agent	17.08 s	17.06 s	[-0.8%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	16.17 s	16.16 s	[-0.8%; +0.9%] (no difference)

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

[sarahchen6]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-11-05 19:14:57 UTC ℹ️ Start processing command /merge

---

2026-11-05 19:15:02 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-11-05 20:22:08 UTC ℹ️ MergeQueue: This merge request was merged