Ullrich Hafner (2025-04-09 21:05):
Yes, you are right. It makes sense to switch to Java 21 in the next
couple of months (actually I never understood why one should not
directly move from Java 11 to Java 21 for the controllers, as we also
fully support Java 21 from the beginning of the Java 17 switch). The
plan is to switch the weekly Jenkins releases to Java 21 in the middle
of this year.
See
https://www.jenkins.io/blog/2023/11/06/introducing-2-2-2-java-support-plan/
If you find such wrong references of the Java version in out
documentation it would be helpful if you can either create an issue in
Jira or even better: click the „Improve the page“ button and fix the
corresponding page by yourself. This helps us a lot as the
documentation is spread along a lot of different files...
The link does explain a bit, thanks. It talks about dropping JDK11, though.
As for the docs updates, I really don't know what problems come with the
upgrade, so I can't write about that. Should I expect everything to just
work? Will all plugins work? Is there a tester script for this? Are
popular plugins tested with various versions of Java automatically?
I saw the video on upgrading to JDK17 (linked in the docs
<https://www.jenkins.io/doc/book/platform-information/upgrade-java-to-17/index.html>),
and it just talks about how to check my Java version and how to make
sure the main node and builder nodes use the same Java version (which is
helpful but doesn't explain much). It does seem like a very manual
process to verify the upgrade.
Cheers,
Maciej Nux
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/jenkinsci-users/edbc9be6-4eac-43e0-8850-ec57767ad612%40mol.com.pl.
