Add semaphore block for ducktape tests

[k-raina]

Why

This PR enables automated performance testing of the Kafka Python client using the ducktape distributed testing framework.

What's Added

New Semaphore CI Block

• Job: "Standard Ducktape Producer Tests"
• Environment: Linux x64 with Python 3.9
• Kafka Setup: KRaft mode (controller-less) for faster startup
• Dependencies: ducktape, psutil, confluent-kafka with librdkafka

Environment-Based Benchmark Configuration

• Local Environment: Relaxed thresholds for development (1000 msg/s, 2000ms latency)
• CI Environment: Strict production-like bounds (1500 msg/s, 1500ms latency)
• Auto-Detection: CI automatically uses stricter bounds, local defaults to relaxed

Technical Implementation

Files Added/Modified

• .semaphore/semaphore.yml - New ducktape CI block with KRaft Kafka setup
• tests/ducktape/benchmark_bounds.json - Environment-based performance bounds
• tests/ducktape/benchmark_metrics.py - Environment detection logic
• tests/ducktape/run_ducktape_test.py - Enhanced test runner with error handling
• tests/docker/docker-compose.ducktape.yml - Dedicated KRaft Kafka for CI

Testing PR

• When bounds are violated -> Pipeline fails check link
• When bounds are not voilated -> Pipeline passes link

Benefits

• Automated Performance Monitoring: Catches performance regressions in CI
• Extensible: Easy to add new environments and customize thresholds

Usage Examples

# Default (local development)
python tests/ducktape/run_ducktape_test.py

# CI environment (automatic in Semaphore)
BENCHMARK_ENVIRONMENT=ci python tests/ducktape/run_ducktape_test.py

# Custom environment
BENCHMARK_ENVIRONMENT=staging python tests/ducktape/run_ducktape_test.py

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[Copilot]

Pull Request Overview

This PR adds a new Ducktape performance test block to the Semaphore CI configuration to enable testing of the confluent-kafka Python client using the ducktape framework.

• Adds a new CI job for running ducktape performance tests on Linux x64
• Configures environment setup including Python 3.9, ducktape framework, and Kafka cluster
• Implements test execution with CI-specific benchmark bounds configuration

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The hardcoded path 'tests/docker/docker-compose.yaml' in the timeout command doesn't match the working directory change in line 316. Since the script changes to 'tests/docker', the path should be relative: 'docker-compose.yaml' or use an absolute path.

Suggested change

	- timeout 60 bash -c 'until docker-compose -f tests/docker/docker-compose.yaml exec -T kafka kafka-topics --bootstrap-server localhost:9092 --list >/dev/null 2>&1; do echo "Waiting for Kafka..."; sleep 5; done'
	- timeout 60 bash -c 'until docker-compose -f docker-compose.yaml exec -T kafka kafka-topics --bootstrap-server localhost:9092 --list >/dev/null 2>&1; do echo "Waiting for Kafka..."; sleep 5; done'

[Copilot]

The BENCHMARK_BOUNDS_CONFIG environment variable is being set twice - once in the env_vars section (line 290) and again as an export command. The duplicate export is redundant since the environment variable is already configured at the block level.

Suggested change

- export BENCHMARK_BOUNDS_CONFIG=tests/ducktape/ci_bounds.json

[sonarqube-confluent]

Analysis Details

1 Issue

• 0 Bugs
• 0 Vulnerabilities
• 1 Code Smell

Coverage and Duplications

• No coverage information (66.40% Estimated after merge)
• No duplication information (5.60% Estimated after merge)

Project ID: confluent-kafka-python

View in SonarQube

[fangnx]

Out of curiosity, how is the machine type chosen?

[k-raina]

"s1-prod-" this is a production grade system, which is used by other semaphore jobs. IMO, its already timetested for this repository, so we should keep using it.

[fangnx]

For my knowledge, is this the cluster dedicated for kafka testing? https://github.com/search?q=org%3Aconfluentinc%204L6g3nShT-eMCtK--X86sw&type=code

[k-raina]

Yes Each CI job spins up its own isolated Kafka container with this ID