Status: Closed (View Workflow)
We recently upgrade our Jenkins server to Jenkins 2.249.2 and updated all plugins, and we're left with a few puzzling notifications about plugins being held back as UNAVAILABLE:
But they all declare requirements for Jenkins 2.249.1 or earlier...
Still shows as `UNAVAILABLE` for me in the Jenkins plugins-manager as of this moment.
We've just updated to 2.249.3 and all plugins, and the only remaining "unavailable" one is Basic Steps v2.23, which we'd expect since it requires latest Jenkins, not just LTS.
This is still an issue with LTS Jenkins 2.249.3 and Pipeline 2.23 which requires Jenkins 2.263 or newer.
Release date: 2020-11-06
- This plugin now requires Jenkins 2.263 or newer
From https://www.jenkins.io/changelog-stable/ (this ticket in bold):
What's new in 2.249.3 (2020-11-04)
139 6 2 !https://www.jenkins.io/images/changelog/storm.png!Community reported issues: 1×
JENKINS-54445 1× JENKINS-54545 1× JENKINS-63941 * Fix extensions footer location (regression in 2.235.1). (pull 4949, pull 5001, issue 63798)
- Show display names in change list again (regression in 2.249.1). (issue 63712)
- Prevent radio buttons from moving when they are clicked. (issue 63332)
After checking for plugin upgrades today I find there are now two plugins showing as UNAVAILABLE
- Pipeline: Basic Steps
I had this happen to me too, after I'd upgraded to 2.249.3 and tried to upgrade all the plugins. But in my case there were about 30 plugins showing as unavailable. I had to manually download and install a handful (AWS SDK -> Jackson -> SnakeYAML) so that my custom plugin had the version of the AWS SDK plugin that it needed.
I just went back to check the list again (two days later) and everything is showing on the Updates tab as usual, ready to install, nothing "unavailable". The only thing that's happened since I last looked was a restart (although I had restarted around five times while installing each plugin manually above, and it definitely didn't help).
Perhaps there was some periodic task that refreshed the metadata to fix the problem?
bryceman: just curious, has your list fixed itself as well or do you still have the problem?