Plugin update "Jenkins (2.323) or higher required"

[Stefan Coussens]

Hi,

We are using the LST cycle but this gives issues when I try to update plugins.

My use case:

Ansible playbook updates the linux server (and jenkins LST if available)

After that I use an ansible playbook to (https://github.com/wcm-io-devops/ansible-jenkins-facts) look for plugins where "hasUpdate = true" and then update the plugin.

This has failed a couple of times and when jenkins loads I get :

XXX Plugin 
Jenkins (2.323) or higher required

What method returns if an plugin is compatible with the current version of jenkins?

(https://javadoc.jenkins.io/hudson/model/UpdateSite.Plugin.html)

What does "isForNewerHudson()" do?

I think I want the 

isCompatible()

Returns true if the plugin and its dependencies are fully compatible with the current installation This is set to restricted for now, since it is only being used by Jenkins UI or Restful API at the moment.

field/method but this is restricted ;(

Any one that can help?

kind regards

Stefan

[Mark Waite]

On Tuesday, March 8, 2022 at 4:44:32 AM UTC-7 Stefan wrote:

Hi,

We are using the LST cycle but this gives issues when I try to update plugins.

My use case:

Ansible playbook updates the linux server (and jenkins LST if available)

After that I use an ansible playbook to (https://github.com/wcm-io-devops/ansible-jenkins-facts) look for plugins where "hasUpdate = true" and then update the plugin.

I think you may be using the wrong tool to update your Jenkins plugins.

https://www.jenkins.io/blog/2022/02/10/last-plugin-version-not-installable/ describes the same type of failure you're seeing.

I think you want to call the plugin installation manager tool to update your plugins.  It takes a Jenkins version number as an argument and will not offer a plugin update if the plugin does not support that Jenkins release.

Mark Waite

[Daniel Beck]

#isForNewerHudson is a reasonable idea, but with the improved update site tiering that should only matter for 3rd party update sites, outdated releases of Jenkins (>12 months), or misconfigured instances.

Make sure you access update-center.json URLs with the ?version query parameter and specify which version of Jenkins you're on unless you track the latest release. Jenkins does that automatically, if you bypass Jenkins you need to add this.

Docs: https://github.com/jenkins-infra/update-center2/tree/master/site