Extend poll time for Maven Central artifact verification job

[sarahchen6]

What Does This Do

Extend the poll time for the verify_maven_central_deployment job to check every 5 min for 45 min.

Motivation

The publishing job takes ~20 min to execute after manually publishing the artifact from staging, so previously we always had to re-run the job. By extending the poll-time to 45 min, we should catch most deployments without running the job infinitely.

Additional Notes

The job can still be manually re-run if publishing takes > 45 min.

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: [PROJ-IDENT]

[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.78 s	14.66 s	[+0.0%; +1.6%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.51 s	13.72 s	[-2.4%; -0.7%] (maybe better)
startup:petclinic:appsec:Agent	17.40 s	17.21 s	[+0.2%; +2.0%] (maybe worse)
startup:petclinic:iast:Agent	17.35 s	17.49 s	[-1.7%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	17.38 s	17.39 s	[-1.1%; +1.0%] (no difference)
startup:petclinic:sca:Agent	16.58 s	17.23 s	[-8.1%; +0.5%] (no difference)
startup:petclinic:tracing:Agent	16.04 s	16.72 s	[-8.2%; +0.1%] (no difference)

Commit: f22754f2 · 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-datadog-prod-us1-2]

More details

The release gate now performs an immediate Maven Central check followed by nine five-minute waits, allowing the tenth and final check at 45 minutes. Adversarial simulations confirmed the terminal failure and final-attempt success paths, and the CI YAML parses successfully.

Was this helpful? React 👍 or 👎

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

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

[sarahchen6]

/merge -f --reason "Gitlab config change - no benefit from extended MQ test suite"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-05 20:11:31 UTC ℹ️ Start processing command /merge -f --reason "Gitlab config change - no benefit from extended MQ test suite"

---

2026-08-05 20:11:36 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

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

Warning

This change was merged without running any pre merge CI checks

Reason: Gitlab config change - no benefit from extended MQ test suite