-
Notifications
You must be signed in to change notification settings - Fork 132
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
[hotfix] Synchronize CI pipeline setup #78
Conversation
.github/workflows/push_pr.yml
Outdated
strategy: | ||
matrix: | ||
flink: [ 1.17.1, 1.18.0 ] | ||
uses: apache/flink-connector-shared-utils/.github/workflows/python_ci.yml@ci_utils | ||
with: | ||
flink_version: ${{ matrix.flink }} |
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.
should we remove ci for python part?
IIRC currently it is done separately
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.
Oh wow I completely missed the Python part. Let me check
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.
I think we should keep them in for PRs, and actually we should also have them for weekly runs.
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.
+1
since it is touched a couple of more ideas
|
The Flink Kafka connector now tests: - All PRs against `main` are tested against Flink `1.17.2` and `1.18.1`, instead of `1.17.1` and `1.18.0` - The weekly run tests -- `main` against `1.17-SNAPSHOT, `1.18-SNAPSHOT` and `1.19-SNAPSHOT` (1.19 is newly added) -- `v3.0` against `1.17-SNAPSHOT` and `1.18-SNAPSHOT` (as was before)
3a66a05
to
070127f
Compare
I think we should mirror what we do with Flink, so I think we should indeed also run them for JDK11 and JDK17? We could argue that JDK11/JDK17 would only be run during a weekly, to avoid overly hitting the servers. I believe we also run those tests during the nightly builds for Flink
We should indeed |
yeah... initially there were already 2 jdks (8, 11) in ci for PRs and that's why I've just added other jdks there... it would make sense to follow something similar we have in Flink main repo where everything is built with jdk8 for PRs and all other jdks are participating only during nightlies |
The Flink Kafka connector now tests:
main
are tested against Flink1.17.2
and1.18.1
, instead of1.17.1
and1.18.0
main
against1.17-SNAPSHOT,
1.18-SNAPSHOTand
1.19-SNAPSHOT(1.19 is newly added) --
v3.0against
1.17-SNAPSHOTand
1.18-SNAPSHOT` (as was before)