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

new location for list of supported versions #3683

Closed
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ In particular, the LTS Release Line is based on slightly older releases to provi
* *Building against recent Jenkins versions* allows you to use recently added core features and API from your plugin.
You will also use that newer version for `mvn hpi:run`, so it may be easier to test your plugin with newer Jenkins releases.
Additionally, since features are sometimes moved from core into plugins, depending on a more recent Jenkins version will make your plugin's dependencies on what used to be core features explicit, otherwise your plugin will not work.
* *Use at least the minimum version supported by the update center*, the supported update center versions can be found at link:https://updates.jenkins.io[updates.jenkins.io], at the time of writing (2020-03) this is 2.164.x.
* *Use at least the minimum version supported by the update center*, the supported update center versions can be found at link:https://updates.jenkins.io/tiers.json[updates.jenkins.io/tiers.json], at the time of writing (2020-09-02) this is 2.176.2.

There are link:https://stats.jenkins.io/pluginversions/[statistics of core versions by plugin] that can help you decide.

Expand Down