This PR is making the CDK to use SemVer.
It requires the contributor to manually set the CDK version allowing to define patch/minor/major version.
This is a first step into improving the way we manage the CDK versioning.
The changes are the following ones:
java-bulk-cdk-publish.yml: remove the autogeneration of the version. Add a check step to ensure that we don't override the latest version
java-cdk-tests.yml: add a step in the CDK CI to ensure that the we don't override existing version.
README.md: Update the doc
build.gradle: remove the task which generate the build number; add a task to check the version doesn't conflict with the latest version.
Co-authored-by: Davin Chia <davinchia@gmail.com>
Any Java CDK changes should also trigger tests on JVM connectors whose CDK versions are set to local.
This helps CDK developers understand when they are stepping on connector developer toes when both the CDK and Connectors are being worked on eagerly.
- Modify the get_modified_connectors script to accept a local-cdk flag telling it to 'detect' connectors on local CDK. This is correct behaviour since the Connector has in fact changed, as the CDK has changed, even though the connector doesn't have direct code changes.
- Modify the regular connector ci check workflow to notice cdk changes and test connectors on local CDK.
I experimented with a gradle approach here and concluded it was more suited for local development than CI, since all the tests would be run within a single job which means 1) longer test execution 2) more confusing test output.
Co-authored-by: Aaron ("AJ") Steers <aj@airbyte.io>
