You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Test JGit 7.0.0-m2 pre-release with Java 17 build
JGit 7.0.0 requires Java 17. Jenkins 2.463 requires Java 17.
Use the plugin bill of materials from 2.462.x because it is the closest
we have to 2.463. The plugin is expected to work with any release 2.463
or later.
* Test JGit 7.0.0 with Jakarta EE 9 Jenkins core
* Use JGit 7.0.0.202408202050-m3 pre-release
* Use JGit 7.0.0.202409031743-r
* Adapt to removed API's in JGit 7.0.0
* Use test harness 2265.x
* Next Jenkins baseline will be a .1
* Use JGit 7.0.0 with Java 17
JGit 7.0.0 requires Java 17. Jenkins 2.463 requires Java 17.
Use the plugin bill of materials from 2.462.x because it is the closest
we have to 2.463. The plugin is expected to work with any release 2.463
or later.
Adapt to removed API's in JGit 7.0.0 by replacing calls to removed API's
with the recommended equivalents.
Tested in my development environment and no issues detected. Tests run
from a container based Jenkins controller with Windows, Linux, and FreeBSD
agents. Tests ran on multiple weekly releases of Jenkins since 2.463.
The Linux agents include:
* Alpine
* Debian Linux 11, 12, testing, and unstable
* openSUSE
* Red Hat Enterprise Linux 8
* Rocky Linux 9
* Ubuntu 20.04, 22.04, and 24.04
* Use 6.1.0 as version
* Use Java 17 features in source code
https://docs.openrewrite.org/running-recipes/popular-recipe-guides/migrate-to-java-17
provided the transformations and they all pass automated tests.
Several nice readability improvements are provided by Java 17.
* Require Jenkins 2.477
* Use test harness that drops EE 8
* Use Jenkins test harness 2289.x
* Use test harness 2299.*
* Use parent pom 5.0
Removes a few of the workarounds since it is released.
* Security scan not ready for Java 17 and Jakarta EE 9
* Use parent pom 5.1
https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-5.1 notes
that it includes a workaround the outdated ASM API inclusion that Guice
brings into Jenkins core. Has not affected the git client plugin, but it
is good to remain current with the most recent release of the parent pom.
* Revert "Security scan not ready for Java 17 and Jakarta EE 9"
Cheeck if security scan is ready for Java 17 and Jakarta EE 9
This reverts commit 4bcca7e.
* Use StaplerRequest2 for EE 9
No need to rely on the compatibility layer for EE 8
---------
Co-authored-by: git-client-user <git-client-user@example.com>
0 commit comments