Skip to content

Skip latest broken Kafka Connect 7.x POMs - #12160

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
masterfrom
alexeyk/skip-broken-kafka-connect-7.5.16
Aug 7, 2026
Merged

Skip latest broken Kafka Connect 7.x POMs#12160
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
masterfrom
alexeyk/skip-broken-kafka-connect-7.5.16

Conversation

@AlexeyKuznetsov-DD

@AlexeyKuznetsov-DD AlexeyKuznetsov-DD commented Aug 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

What Does This Do

Skips the latest broken org.apache.kafka:connect-runtime patch releases from the kafka-connect-0.11 Muzzle compatibility range:

  • 7.5.16-ce and 7.5.16-ccs
  • 7.6.13-ce and 7.6.13-ccs
  • 7.7.11-ce and 7.7.11-ccs
  • 7.8.10-ce and 7.8.10-ccs
  • 7.9.9-ce and 7.9.9-ccs

Motivation

Unblocks Muzzle CI. The newly published -ce POMs depend on unavailable Jetty 9.4.60 artifacts, while the -ccs POMs depend on unavailable Jetty 9.4.63 artifacts.

Additional Notes

This is the same upstream broken-POM issue handled previously in:

The upstream issue is tracked in confluentinc/kafka-connect-storage-common#468.

Validation:

  • :dd-java-agent:instrumentation:kafka:kafka-connect-0.11:muzzle — 28 passed, 0 failed
  • :dd-java-agent:instrumentation:kafka:kafka-connect-0.11:spotlessCheck

Contributor Checklist

@AlexeyKuznetsov-DD AlexeyKuznetsov-DD added type: bug fix Bug fix tag: no release notes Changes to exclude from release notes inst: kafka Kafka instrumentation tag: ai generated Largely based on code generated by an AI or LLM tag: dependencies Dependencies related changes labels Aug 7, 2026
@AlexeyKuznetsov-DD
AlexeyKuznetsov-DD marked this pull request as ready for review August 7, 2026 14:15
@AlexeyKuznetsov-DD
AlexeyKuznetsov-DD requested review from a team as code owners August 7, 2026 14:15
@AlexeyKuznetsov-DD
AlexeyKuznetsov-DD requested review from ValentinZakharov and removed request for a team August 7, 2026 14:15
@datadog-official

datadog-official Bot commented Aug 7, 2026 •
edited by datadog-prod-us1-3 Bot
Loading

Copy link
Copy Markdown
Contributor

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 69.74% (+11.81%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 079a565 | Docs | Datadog PR Page | Give us feedback!

@dd-octo-sts

dd-octo-sts Bot commented Aug 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🟢 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.04 s 13.95 s [-0.3%; +1.5%] (no difference)
startup:insecure-bank:tracing:Agent 12.97 s 12.96 s [-0.6%; +0.7%] (no difference)
startup:petclinic:appsec:Agent 16.87 s 16.75 s [-0.2%; +1.6%] (no difference)
startup:petclinic:iast:Agent 16.93 s 16.95 s [-1.0%; +0.7%] (no difference)
startup:petclinic:profiling:Agent 16.88 s 16.99 s [-1.9%; +0.7%] (no difference)
startup:petclinic:sca:Agent 16.75 s 16.50 s [+0.3%; +2.7%] (maybe worse)
startup:petclinic:tracing:Agent 15.62 s 16.14 s [-7.3%; +0.9%] (no difference)

Commit: 079a565f · 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 AlexeyKuznetsov-DD changed the title Skip broken Kafka Connect 7.5.16 POMs Skip latest broken Kafka Connect 7.x POMs Aug 7, 2026
datadog-official[bot]
datadog-official Bot reviewed Aug 7, 2026
View reviewed changes

@datadog-official datadog-official Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Datadog Autotest: PASS

More details

Both 7.5.16 variants are exact-skipped while neighboring unsuffixed and future versions remain eligible, and Muzzle continues to enforce the supported and inverse Kafka Connect ranges.

Was this helpful? React 👍 or 👎

📊 Validated against 10 scenarios · Open Bits AI session

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

@pr-commenter

pr-commenter Bot commented Aug 7, 2026

Copy link
Copy Markdown

Kafka / producer-benchmark

Parameters

Baseline Candidate
baseline_or_candidate baseline candidate
git_branch master alexeyk/skip-broken-kafka-connect-7.5.16
git_commit_date 1786110513 1786113612
git_commit_sha b6650c2 079a565
See matching parameters
Baseline Candidate
ci_job_date 1786114816 1786114816
ci_job_id 1933039140 1933039140
ci_pipeline_id 129651192 129651192
cpu_model Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
jdkVersion 11.0.25 11.0.25
jmhVersion 1.36 1.36
jvm /usr/lib/jvm/java-11-openjdk-amd64/bin/java /usr/lib/jvm/java-11-openjdk-amd64/bin/java
jvmArgs -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=15002 -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=15002 -Dhttp.nonProxyHosts=localhost *.localhost
vmName OpenJDK 64-Bit Server VM OpenJDK 64-Bit Server VM
vmVersion 11.0.25+9-post-Ubuntu-1ubuntu122.04 11.0.25+9-post-Ubuntu-1ubuntu122.04

Summary

Found 0 performance improvements and 0 performance regressions! Performance is the same for 3 metrics, 0 unstable metrics.

See unchanged results
scenario Δ mean throughput
scenario:not-instrumented/KafkaProduceBenchmark.benchProduce same
scenario:only-tracing-dsm-disabled-benchmarks/KafkaProduceBenchmark.benchProduce same
scenario:only-tracing-dsm-enabled-benchmarks/KafkaProduceBenchmark.benchProduce same

@pr-commenter

pr-commenter Bot commented Aug 7, 2026

Copy link
Copy Markdown

Kafka / consumer-benchmark

Parameters

Baseline Candidate
baseline_or_candidate baseline candidate
git_branch master alexeyk/skip-broken-kafka-connect-7.5.16
git_commit_date 1786110513 1786113612
git_commit_sha b6650c2 079a565
See matching parameters
Baseline Candidate
ci_job_date 1786114853 1786114853
ci_job_id 1933039141 1933039141
ci_pipeline_id 129651192 129651192
cpu_model Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
jdkVersion 11.0.25 11.0.25
jmhVersion 1.36 1.36
jvm /usr/lib/jvm/java-11-openjdk-amd64/bin/java /usr/lib/jvm/java-11-openjdk-amd64/bin/java
jvmArgs -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=15002 -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=15002 -Dhttp.nonProxyHosts=localhost *.localhost
vmName OpenJDK 64-Bit Server VM OpenJDK 64-Bit Server VM
vmVersion 11.0.25+9-post-Ubuntu-1ubuntu122.04 11.0.25+9-post-Ubuntu-1ubuntu122.04

Summary

Found 0 performance improvements and 0 performance regressions! Performance is the same for 3 metrics, 0 unstable metrics.

See unchanged results
scenario Δ mean throughput
scenario:not-instrumented/KafkaConsumerBenchmark.benchConsume same
scenario:only-tracing-dsm-disabled-benchmarks/KafkaConsumerBenchmark.benchConsume same
scenario:only-tracing-dsm-enabled-benchmarks/KafkaConsumerBenchmark.benchConsume same

@AlexeyKuznetsov-DD

AlexeyKuznetsov-DD commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

/merge -f --reason "Fixed Muzzle, no need to wait for MQ, since we skip Muzzle on MQ"

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Aug 7, 2026 •
edited
Loading

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-08-07 15:45:48 UTC ℹ️ Start processing command /merge -f --reason "Fixed Muzzle, no need to wait for MQ, since we skip Muzzle on MQ"

2026-08-07 15:45:52 UTC ℹ️ MergeQueue: pull request added to the queue

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

2026-08-07 15:46:01 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: Fixed Muzzle, no need to wait for MQ, since we skip Muzzle on MQ

@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 19bad93 into master Aug 7, 2026
616 of 618 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the alexeyk/skip-broken-kafka-connect-7.5.16 branch August 7, 2026 15:46
@github-actions github-actions Bot added this to the 1.66.0 milestone Aug 7, 2026
@kaahos kaahos mentioned this pull request Aug 10, 2026
Merged
PerfectSlayer pushed a commit that referenced this pull request Aug 10, 2026
@kaahos @AlexeyKuznetsov-DD
Skip latest broken Kafka Connect 7.x POMs (#12160) (#12172)
db887be 
Skip broken Kafka Connect 7.5.16 POMs

Skip remaining broken Kafka Connect POMs


(cherry picked from commit 19bad93)

Co-authored-by: Alexey Kuznetsov <alexey.kuznetsov@datadoghq.com>
@AlexeyKuznetsov-DD AlexeyKuznetsov-DD mentioned this pull request Aug 10, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@datadog-official datadog-official[bot] datadog-official[bot] left review comments
@sarahchen6 sarahchen6 sarahchen6 approved these changes
@ValentinZakharov ValentinZakharov Awaiting requested review from ValentinZakharov ValentinZakharov is a code owner automatically assigned from DataDog/apm-idm-java

Assignees

No one assigned

Labels

inst: kafka Kafka instrumentation tag: ai generated Largely based on code generated by an AI or LLM tag: dependencies Dependencies related changes tag: no release notes Changes to exclude from release notes type: bug fix Bug fix

Projects

None yet

Milestone

1.66.0

Development

Successfully merging this pull request may close these issues.

2 participants

@AlexeyKuznetsov-DD @sarahchen6