Stop running all SSI system test VMs on MQ

[sarahchen6]

What Does This Do

Run all SSI GitLab system tests on master only, no longer on the Merge Queue

Motivation

These tests are relatively flaky and difficult to mark as flaky on the dd-trace-java side. They are negatively affecting MQ success rates. The tests were intended to be run nightly, so running only on master should be okay.

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

[datadog-datadog-prod-us1]

More details

Three-line CI config deletion that removes SYSTEM_TESTS_RUN_ALL_VMS: "true" from the MQ workflow rule — the downstream system-tests pipeline (via remote one-pipeline.yml) will now use its default VM set on MQ while master retains the full-VM run; the Gradle test_ssi_smoke jobs continue running on MQ unaffected because they have their own explicit rules and do not consume this variable.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 1648cdd · What is Autotest? · Any feedback? Reach out in #autotest}

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 57.17% (-0.02%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 1648cdd | Docs | Datadog PR Page | Give us 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	13.92 s	14.03 s	[-1.4%; -0.1%] (maybe better)
startup:insecure-bank:tracing:Agent	13.02 s	13.06 s	[-1.1%; +0.6%] (no difference)
startup:petclinic:appsec:Agent	16.89 s	16.21 s	[-0.2%; +8.7%] (no difference)
startup:petclinic:iast:Agent	16.80 s	16.96 s	[-1.7%; -0.2%] (maybe better)
startup:petclinic:profiling:Agent	16.81 s	16.66 s	[-0.2%; +2.0%] (no difference)
startup:petclinic:sca:Agent	16.93 s	16.91 s	[-0.7%; +0.9%] (no difference)
startup:petclinic:tracing:Agent	16.17 s	16.33 s	[-1.8%; -0.2%] (maybe better)

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

[mcculls]

Makes sense

[sarahchen6]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-14 17:11:52 UTC ℹ️ Start processing command /merge

---

2026-07-14 17:11:57 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-07-14 18:13:08 UTC ℹ️ MergeQueue: This merge request was merged