Jenkins migration

[cprovencher]

Action required after merging

These changes will be pint merged automatically when this PR is merged, but be on the lookout for automated PRs like this one in case pint runs into merge conflicts.

Changes

1. backporting migration changes from master
2. deleting Jenkinsfile
3. adding generate_connect_changelog: true

Ticket

https://confluentinc.atlassian.net/browse/CC-23571

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sonarqube-confluent]

• 0.00% Coverage on New Code (is less than 80.00%)

Analysis Details

72 Issues

• 7 Bugs
• 0 Vulnerabilities
• 65 Code Smells

Coverage and Duplications

• 0.00% Coverage (0.00% Estimated after merge)
• 0.66% Duplicated Code (0.70% Estimated after merge)

Project ID: kafka-connect-storage-common

View in SonarQube