Require Jenkins 2.387.3 or newer #293
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The existing plugins that depend on the config file provider plugin have a wide range of Jenkins minimum versions. As far as I can tell, increasing the Jenkins minimum required version from 2.361.4 to 2.387.3 will not create a problem for most users of the plugin. Users that are running recent versions of the plugin are already using Jenkins 2.387.3 or newer. Users that are running much older versions are not upgrading the plugin version so won't be affected by an increase of minimum Jenkins version because they probably won't install the new plugin release. https://stats.jenkins.io/pluginversions/config-file-provider.html shows * 34% of all installations of the config file provider plugin are already running Jenkins 2.387.3 or newer. Those users will be able to upgade to the version that requires Jenkins 2.387.3 without changing their Jenkins core version * 94% of the 11900 installations of the most recent release (953.xxx) are already running Jenkins 2.387.3 or newer. * 93% of the 11700 installations of the next most recent release (952.xxx) are already running Jenkins 2.387.3 or newer. Plugins that depend on the config file provider plugin include: * Artifactory - requires 2.235.5 or newer, no additional problems when requiring 2.387.3 or newer * Ivy - requires 2.361.4 or newer, with open security vulnerability and up for adoption * JClouds - requires 2.332.1 or newer, no additional problems when requiring 2.387.3 or newer * Managed Scripts - requires 2.319.3 or newer, no additional problems when requiring 2.387.3 or newer * NodeJS - already requires 2.387.3 or newer * OpenStack Cloud 0 requires 2.289.1 or newer, no additional problems when requiring 2.387.3 or newer * Pipeline Dependency Walker - requires 1.642.4 or newer, no additional problems when requiring 2.387.3 or newer * Pipeline Maven Integration - requires 2.361.4 or newer * Pipeline NPM Integration - already requires 2.387.3 or newer * Pipeline: Multibranch with defaults - requires Jenkin 2.130 or newer, no additional problems when requiring 2.387.3 or newer
olamy
approved these changes
Sep 17, 2023
alecharp
approved these changes
Sep 18, 2023
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Require Jenkins 2.387.3 or newer
The existing plugins that depend on the config file provider plugin have a wide range of Jenkins minimum versions. As far as I can tell, increasing the Jenkins minimum required version from 2.361.4 to 2.387.3 will not create a problem for most users of the plugin.
Users that are running recent versions of the plugin are already using Jenkins 2.387.3 or newer.
Users that are running much older versions are not upgrading the plugin version so won't be affected by an increase of minimum Jenkins version because they probably won't install the new plugin release.
https://stats.jenkins.io/pluginversions/config-file-provider.html shows
Plugins that depend on the config file provider plugin include:
Testing done
Confirmed automated tests pass on my Linux machine with Java 11 and Java 17.
Submitter checklist