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

Update Jenkins LTS versions to 2.479.2 in various parts of the documentation #7768

Merged
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 @@ -13,7 +13,7 @@ You need to balance compatibility and features:
In particular, the LTS Release Line is based on slightly older releases to provide a more stable experience for conservative users.
* *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.
* *Do not use versions no longer supported by the update center*, which is currently anything older than 2.430 for weekly releases, and 2.414.3 for LTS releases.
* *Do not use versions no longer supported by the update center*, which is currently anything older than 2.432 for weekly releases, and 2.426.1 for LTS releases.
Note that the lowest supported version changes about every week (weekly release) or every month (LTS release), so these specific versions will be a bad choice soon.
* *Prefer an LTS version over weekly versions.*
** If you are based on the _currently active_ LTS line,
Expand All @@ -32,7 +32,7 @@ These are updated monthly.
When updating the core dependency, choose the link:/changelog-stable/[newest LTS version] that doesn't exclude a majority of your existing users (by requiring a newer Jenkins than they have).

NOTE: If you are packaging a pure API library (one that does not depend on Jenkins APIs) then you should ignore newer Jenkins versions and pick an older LTS.
Something around 1 year old that does not have too many detached plugins makes a good choice and 2.414.3 would be a reasonable candidate.
Something around 1 year old that does not have too many detached plugins makes a good choice and 2.426.3 would be a reasonable candidate.

## Currently recommended versions

Expand Down