sem trigger

[Shubham Kalla (Kalla-Shubham)]

Problem

Developer want to test his changes in the connector against KDP test cases. This makes a good pr gating option to ensure nothing is breaking end to end from a particular dev change.

Solution

A separate task has been created which gets trigger from sem trigger to run the mapped KDP test cases for the connector changes.

Does this solution apply anywhere else?

• yes
• no

If yes, where?

Test Strategy

Testing done:

• Unit tests
• Integration tests
• System tests
• Manual tests

Release Plan

[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 CI block to trigger the connector jar tests via a sem-trigger command when a pull request is raised, ensuring end‐to‐end validation of connector changes.

• Added a new CI gating block ("Connector Jar Build CI Gating") in the semaphore configuration.
• Incorporated a sem-trigger command to invoke the Connect Jar KDP Test Task using specified parameters.

Comments suppressed due to low confidence (1)

.semaphore/semaphore.yml:92

• [nitpick] The trailing semicolon in the sem-trigger command may be unnecessary and could affect the shell command execution; please verify if it is required.

              -w; \

[sonarqube-confluent]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• No coverage information (81.90% Estimated after merge)
• No duplication information (2.90% Estimated after merge)

Project ID: kafka-connect-jdbc

View in SonarQube