-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BP-1.17][FLINK-18356] Update CI image #23757
Conversation
@flinkbot run azure |
The license check failure cannot be reproduced locally. Let's see whether it's reproducible in CI. |
b134356
to
4ae9836
Compare
I cannot get my head around why just upgrading the Docker image (4ae9836) leads to a LicenseCheck failure. We have to backport FLINK-32834 and FLINK-28203 to fix CI. Update: Ok, looking into the issues: FLINK-28203 has to be backported because of the Maven version update. But the LicenseChecker issue seems to be unrelated. I still have to investigate whether FLINK-32834 is actually not needed. Update 2: Looks like backporting FLINK-32834 is actually not necessary and I was misguided by error initially. |
4ae9836
to
897fd9a
Compare
Thanks for driving this 👍 After looking at FLINK-28203 i noticed that there are also files shouldn't they also be part of this PR? |
f8054a4
to
48cc6f7
Compare
You're right. Thanks for this thorough review. I screwed up the backports. But anyway, @zentol pushed a dedicated image for the |
# (see chesnay/flink-ci:java_8_11_17_maven_386_v3 which is used in branches for | ||
# Flink 1.18+) but still use Maven 3.2.5 (to avoid backporting FLINK-28016) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
should we refer to concrete image here?
I'm asking since now there is a new one available chesnay/flink-ci:java_8_11_17_21_maven_386
which potentially could be used for 1.19
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point - I had the naive view that we won't change the Docker image anymore until the EOL of 1.17 :-D
Thanks for the update |
48cc6f7
to
be3c880
Compare
What is the purpose of the change
1.17 backport PR for parent PR #23717
Brief change log
I also backport the change for the docs build for the sake of consistency even though it's not necessary to fix FLINK-18356.
This backport required the upgrade of Maven to 3.8.6 (FLINK-28203).
Verifying this change
CI should pass without problems and should include the optional check
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: noDocumentation