Run arm64 tests on merge queue and master

[AlexeyKuznetsov-DD]

What Does This Do

Reworks the rules in the shared .test_job_arm64 template (inherited by all arm64 test jobs) so they trigger in three contexts:

• MergeQueue (mq-working-branch-*): full matrix — both default and non-default JVMs — running on_success (gating).
• master: default JVMs (8, 11, 17, 21, 25, tip) running on_success (gating).
• Merge requests: default JVMs available as manual, allow_failure: true (non-blocking).

ibm8/oracle8 are excluded across all variants via a single top guard rule (when: never) since no arm64 images are published upstream.

Motivation

Previously arm64 jobs were manual + allow_failure only, so arm64 was never exercised automatically. This gives real coverage: the full JVM matrix runs in the merge queue, default JVMs gate master, and developers can still trigger default-JVM runs manually on MRs.

Additional Notes

arm64 tested on GitLab manually for ~1 month, no issues so far, let's give a shot.

[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.00 s	13.94 s	[-0.2%; +1.1%] (no difference)
startup:insecure-bank:tracing:Agent	12.89 s	12.93 s	[-1.0%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	16.86 s	16.76 s	[-0.4%; +1.7%] (no difference)
startup:petclinic:iast:Agent	16.81 s	16.39 s	[-1.9%; +7.0%] (no difference)
startup:petclinic:profiling:Agent	16.83 s	16.73 s	[-0.7%; +1.9%] (no difference)
startup:petclinic:sca:Agent	16.78 s	16.76 s	[-0.7%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	16.03 s	16.12 s	[-1.3%; +0.2%] (no difference)

Commit: 207b1939 · 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]

/ddci trigger

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-01 22:20:19 UTC ℹ️ Start processing command /ddci trigger

---

2026-07-01 22:20:23 UTC ℹ️ Devflow: /ddci trigger

Tasks sourcing running asynchronously in workflow devflow:12b7b7cc-f1b5-46b6-994d-79c2c710b517_44:019f1fc4-d372-764e-a94d-e6a964b51039 under run id 019f1fc4-da75-7307-94a0-3bcde3f50b22

[AlexeyKuznetsov-DD]

/merge -f --reason "arm64 MQ & master enabled, no need to re-run"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-02 00:26:12 UTC ℹ️ Start processing command /merge -f --reason "arm64 MQ & master enabled, no need to re-run"

---

2026-07-02 00:26:17 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-07-02 00:26:24 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: arm64 MQ & master enabled, no need to re-run