Update CI for Flink Connector Parent POM 2.0 compatibility#53
Merged
ferenc-csaky merged 1 commit intoapache:ci_utilsfrom Mar 17, 2026
Merged
Update CI for Flink Connector Parent POM 2.0 compatibility#53ferenc-csaky merged 1 commit intoapache:ci_utilsfrom
ferenc-csaky merged 1 commit intoapache:ci_utilsfrom
Conversation
* Adds CI step which will activate the java11-taget profile if JDK 11 is selected * Updates both Java and Python CI workflows * Updated various github actions to their latest versions Signed-off-by: Thomas Cooper <code@tomcooper.dev>
davidradl
reviewed
Mar 5, 2026
ferenc-csaky
approved these changes
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With the new Flink Connector Parent POM enforcing Java 17 as the default target, we need to use the
java11-targetprofile when testing against JDK 11. Rather than add this logic to every connector CI, this PR adds that logic here. Connectors using older parent pom versions without thejava11-targetshould just silently ignore the missing profile.This PR also: