We are running an LTS version of Jenkins via docker with agents via ssh. This all works well. When we look at updates, it tells us that there is an updated version of Jenkins available (true, latest LTS is 2.555.2 as of writing) however there does not appear to be a way to filter the jenkins core updates to LTS releases only so it says 2.565 is available. When it looks at the plugins it then says these updates are available but also says some will require 2.556 which is a non-lts release. Is there a way to tell jenkins core to only check for LTS releases? I assume that once that part is set, the avaiable plugin updates would then be filtered correctly based on other comments about it including version in the request to refine the list.
Thanks
Digging a little more at the update-center2/site/LAYOUT.md at 4b2ea778a451ba5b4a58b19f4157c7ae0fdc32a7 · jenkins-infra/update-center2 · GitHub it might be good to include a block for stable here similar to the experimental block Jenkins Update Sites
(I probably dug into this before but due to an update had to revert and since forgot)
Jenkins normally is aware when you use an LTS version and should only offer LTS versions for upgrade. Also for plugins it should only offer plugins that are compatible with the installed version.
Please check the update site url that you have configured in the advanced section of the plugin manager
I think at some point we either started with a non LTS release or changed the the update url off of https://updates.jenkins.io/stable/update-center.json (the docs page I reference says the default is https://updates.jenkins.io/update-center.json) assuming that should be the default for LTS builds. Changing that back? got us to what I expected to be happening. At this point I think my question is 1) does an LTS container start with the correct update site and 2) should the docs page have a callout directly for “stable”/LTS?
Jenkins adds a query parameter with the version it uses. See https://updates.jenkins.io/
This allows to use the same url for both LTS and weekly versions.
I saw that and same comments about that in the forum however see the sceenshot I included. if that was working correctly, I should not have seen any plugins that would require 556. I can doulbe check our proxy setup but the requests I saw included the version numbers.
