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

Require Jenkins 2.401.3 or newer #1530

Merged
merged 1 commit into from
Dec 9, 2023

Conversation

MarkEWaite
Copy link
Contributor

Require Jenkins 2.401.3 or newer

Git client plugin will require 2.401.3 or newer in its next release so that it can depend on the gson-api plugin rather than bundling the gson-api jar file as a transitive dependency for the Eclipse JGit LFS library.

The installation data indicates that most users are already prepared for this change:

  • 42% of all installations of the git plugin are already running Jenkins 2.401.3 or newer
  • 75% of all installations of git plugin 5.0.0 or newer are already running Jenkins 2.401.3 or newer. The git plugin 5.0.0 release was more than 11 months ago
  • 94% of the 107000 installations of git plugin 5.2.0 + 5.2.1 are running on Jenkins 2.401.3 or newer

The majority of git plugin users that are upgrading their plugin version are upgrading to releases of the plugin on Jenkins 2.401.3 or newer.

Security advisories that apply to Jenkins 2.401.2 or 2.387.3 and do not apply to Jenkins 2.401.3 include:

Checklist

  • I have read the CONTRIBUTING doc
  • I have referenced the Jira issue related to my changes in one or more commit messages
  • Unit tests pass locally with my changes
  • I have added documentation as necessary
  • No Javadoc warnings were introduced with my changes
  • No spotbugs warnings were introduced with my changes
  • Documentation in README has been updated as necessary
  • Online help has been added and reviewed for any new or modified fields
  • I have interactively tested my changes
  • Any dependent changes have been merged and published in upstream modules (like git-client-plugin)

Types of changes

  • Maintenance

Git client plugin will soon require 2.401.3 or newer so that it can
depend on the gson-api plugin rather than bundling the gson-api jar
file as a transitive dependency for the Eclipse JGit LFS library.

42% of all installations of the git plugin are already running Jenkins
2.401.3 or newer.

75% of all installations of git plugin 5.0.0 or newer are already
running Jenkins 2.401.3 or newer.  The git plugin 5.0.0 release was
more than 11 months ago.

94% of the 107000 installations of git plugin 5.2.0 + 5.2.1 are
running on Jenkins 2.401.3 or newer.

The majority of git plugin users that are upgrading their plugin
version are upgrading to releases of the plugin on Jenkins 2.401.3 or
newer.

Security advisories that apply to Jenkins 2.401.2 or 2.387.3 and do
not apply to Jenkins 2.401.3 include:

* https://www.jenkins.io/security/advisory/2023-07-26/
* https://www.jenkins.io/security/advisory/2023-06-14/
@MarkEWaite MarkEWaite requested a review from a team as a code owner December 9, 2023 10:58
@MarkEWaite MarkEWaite added the chore Reduces maintenance effort by changes not directly visible to users label Dec 9, 2023
@github-actions github-actions bot added the dependencies Dependency related change label Dec 9, 2023
@MarkEWaite MarkEWaite enabled auto-merge (squash) December 9, 2023 11:21
@MarkEWaite MarkEWaite removed the dependencies Dependency related change label Dec 9, 2023
@MarkEWaite MarkEWaite merged commit b7eeb4e into jenkinsci:master Dec 9, 2023
14 of 15 checks passed
@MarkEWaite MarkEWaite deleted the require-2.401.3-or-newer branch December 19, 2023 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Reduces maintenance effort by changes not directly visible to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant