-
Notifications
You must be signed in to change notification settings - Fork 393
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
Require Jenkins 2.479 or newer #1172
Conversation
3b8f18e
to
b97ab86
Compare
1705b84
to
bb06bc8
Compare
6072abd
to
6bfa95c
Compare
bb06bc8
to
f3ff1ee
Compare
f3ff1ee
to
10fb949
Compare
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.
6bfa95c
to
c14430c
Compare
10fb949
to
7f33b16
Compare
…aite/git-client-plugin into test-jgit-7.0.0-with-jakarta-ee-9
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
Removes a few of the workarounds since it is released.
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.
Cheeck if security scan is ready for Java 17 and Jakarta EE 9 This reverts commit 4bcca7e.
Should also migrate to EE 9: src/main/java/hudson/plugins/git/GitTool.java
30:import org.kohsuke.stapler.StaplerRequest;
156: public boolean configure(StaplerRequest req, JSONObject json) { |
No need to rely on the compatibility layer for EE 8
* jenkinsci/git-client-plugin#1172 * jenkinsci/git-plugin#1671 * jenkinsci/scm-api-plugin#282 Changes method signatures of several methods in the git plugin from x(StaplerRequest) to x(StaplerRequest2), but hoped that there are no consumers of those API's outside the git plugin.
<!-- TODO Replace with the standard jenkins.baseline references after LTS requires Java 17 --> | ||
<!-- <jenkins.version>${jenkins.baseline}.1</jenkins.version> --> |
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.
jenkinsci/bom#3677 IIUC
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.
BOM will release Friday, then I plan to release the git client plugin 6.1.0 using that new plugin BOM release.
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.
Or maybe it is better to release git client plugin 6.1.0 before the weekly BOM so that it is available sooner to BOM consumers
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.
The more I think about it, the more I think it is better to release this today then include it in the plugin BOM release tomorrow
Require Jenkins 2.479 or newer
JGit 7.0.0 requires Java 17 or newer. Jenkins 2.475 requires Java 17 or newer and includes Jetty 12 and Jakarta EE 9. Jenkins 2.479 includes a security fix and is the baseline for the next LTS.
Require the Jenkins weekly is the baseline for the next LTS.
Would be nice to wait on this release until the plugin BOM is available for 2.479.x so that it can depend on the 2.479.x plugin BOM. That should happen in the plugin BOM release 15 Oct 2024.
Testing done
Interactive testing looks good and automated tests all pass.
Submitter checklist