From fc1704624e6bebad697a7a3b7bcfb7459ea6f863 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 19 Dec 2024 19:44:26 +0100 Subject: [PATCH] Update Jenkins LTS versions to 2.479.2 in various parts of the documentation (#7768) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * chore: Bump Jenkins oldest stable supported version in the "Choosing ... ... a version" page Made with ❤️️ by updatecli * chore: Bump Jenkins oldest stable supported version in the "Choosing ... ... a version" page Made with ❤️️ by updatecli * chore: Bump Jenkins oldest weekly supported version in the "Choosing ... ... a version" page Made with ❤️️ by updatecli --------- Co-authored-by: GitHub Actions <41898282+github-actions[bot]@users.noreply.github.com> --- .../plugin-development/choosing-jenkins-baseline.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc b/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc index a789fa4ed140..bc50ba9b0789 100644 --- a/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc +++ b/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc @@ -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, @@ -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