Skip to content
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

Migrate Docker images and CI to Java 17 #14355

Merged
merged 2 commits into from
Apr 21, 2022

Conversation

nicoloboschi
Copy link
Contributor

Motivation

The goal is to run Pulsar using JDK17 at runtime, benefitting from the latest JVM performance improvements and features.
In order to do that we need to run all the tests using JDK17.

The goal is NOT to deprecate JDK8 or JDK11 runtime compatibility. The java compiler release flag doesn't change.

Modifications

  • Build docker images using JDK17 instead of JDK11
  • All the jobs (except for jdk 1.8 compatibility) are now using JDK17

Verifying this change

All the CI jobs are passing
Manual tests are encouraged, mainly around pulsar-io connectors since we don't have integration tests for all the connectors.

Documentation

  • doc

Added the support for JDK17 in the installation page.

@github-actions github-actions bot added the doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. label Feb 17, 2022
@nicoloboschi
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

1 similar comment
@nicoloboschi
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

@nicoloboschi nicoloboschi marked this pull request as ready for review February 25, 2022 10:22
@nicoloboschi
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

@github-actions
Copy link

The pr had no activity for 30 days, mark with Stale label.

@lhotari
Copy link
Member

lhotari commented Mar 31, 2022

@nicoloboschi Please rebase this PR

@nicoloboschi
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

@merlimat merlimat added this to the 2.11.0 milestone Apr 2, 2022
@merlimat merlimat added area/build doc-not-needed Your PR changes do not impact docs labels Apr 2, 2022
@heesung-sn
Copy link
Contributor

Hi nicoloboschi,

I am definitely a latecomer to this issue, but I think we could also support java17 build as well as this java17 runtime support.

I added this java17 build support and created a pip here, #15207.

I can help with upgrading the build for java17 and adding the different jdk compatibility tests (if not done yet).

Copy link
Member

@michaeljmarshall michaeljmarshall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@michaeljmarshall michaeljmarshall merged commit ccfea16 into apache:master Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. doc-not-needed Your PR changes do not impact docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants