Skip the latest broken org.apache.kafka:connect-runtime versions in the kafka-connect-0.11 muzzle test

[AlexeyKuznetsov-DD]

What Does This Do

Skip the latest broken org.apache.kafka:connect-runtime versions in the kafka-connect-0.11 muzzle range: 7.5.15, 7.6.12, 7.7.10, 7.8.9, 7.9.8 (both -ce and -ccs). Same as we did in #11377.

Motivation

Green CI. These newly-released patches have broken POMs depending on the non-existent org.eclipse.jetty:*:9.4.60, so muzzle's AssertPass fails to resolve dependencies (it tests the highest patch of each major.minor line).

Additional Notes

Again the same broken-POM issue, see #11377. The 8.x lines are unaffected (they moved to jetty 12.0.34). Tracked upstream in confluentinc/kafka-connect-storage-common#468.

[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.97 s	13.94 s	[-0.6%; +1.0%] (no difference)
startup:insecure-bank:tracing:Agent	12.94 s	12.95 s	[-0.7%; +0.6%] (no difference)
startup:petclinic:appsec:Agent	17.02 s	16.56 s	[+1.8%; +3.8%] (significantly worse)
startup:petclinic:iast:Agent	17.11 s	17.00 s	[-0.1%; +1.4%] (no difference)
startup:petclinic:profiling:Agent	16.70 s	17.04 s	[-3.1%; -0.9%] (maybe better)
startup:petclinic:sca:Agent	17.01 s	17.00 s	[-0.8%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	16.02 s	16.09 s	[-1.2%; +0.3%] (no difference)

Commit: 3574024a · 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]

/merge -f --reason "Muzzle tests not executed during MQ"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-18 00:12:11 UTC ℹ️ Start processing command /merge -f --reason "Muzzle tests not executed during MQ"

---

2026-06-18 00:12:15 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-06-18 00:12:24 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: Muzzle tests not executed during MQ