Fix race condition with reliability env deploy

[randomanderson]

What Does This Do

There's a race condition with the reliability env deploy introduced with one-pipeline 1.1.0 . deploy_to_reliability_env has needs: [] which means it no longer waits for previous stages to finish. For dd-trace-java, this means the deploy job runs before the build job is finished causing a failure.

This PR adds needs: [ build ] to have the trigger wait for the build to finish

[datadog-datadog-prod-us1]

More details

The reliability deployment override correctly changes the injected job from an empty dependency set to waiting for the build, while preserving the external trigger configuration. Merge-request, scheduled, release-tag, and configuration-merge scenarios all behaved as intended; no additional tests are recommended because this non-runtime YAML change is fully covered by the dependency-graph validation.

Was this helpful? React 👍 or 👎

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

_{🤖 Datadog Autotest · Commit 4bed6f0 · 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.77 s	14.63 s	[+0.1%; +1.7%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.63 s	13.76 s	[-1.7%; -0.1%] (maybe better)
startup:petclinic:appsec:Agent	16.43 s	16.68 s	[-5.9%; +2.8%] (no difference)
startup:petclinic:iast:Agent	16.72 s	16.83 s	[-1.4%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	16.44 s	16.60 s	[-2.0%; +0.1%] (no difference)
startup:petclinic:sca:Agent	16.86 s	16.76 s	[-0.3%; +1.6%] (no difference)
startup:petclinic:tracing:Agent	15.97 s	15.67 s	[-2.5%; +6.3%] (no difference)

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

[randomanderson]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-23 23:58:28 UTC ℹ️ Start processing command /merge

---

2026-07-23 23:58:32 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-07-24 00:54:44 UTC ℹ️ MergeQueue: This merge request was merged