Upgrade problems from 1.651.3 to 2.19.3

[Anders Persson]

After the upgrade some plugins does not load. I get this message:

There are dependency errors loading some plugins:

• Pipeline Graph Analysis Plugin v1.2
  • Pipeline: Groovy v2.2 failed to load. Fix this plugin first.
• Pipeline v2.2
  • Pipeline: Supporting APIs v2.1 failed to load. Fix this plugin first.
• Pipeline: Build Step v2.4
  • Pipeline: Supporting APIs v2.6 failed to load. Fix this plugin first.
• Pipeline: Stage View Plugin v2.3
  • Pipeline: Job v2.0 failed to load. Fix this plugin first.
• Pipeline: Shared Groovy Libraries v2.1
  • Jenkins GIT server Plugin v1.5 failed to load. Fix this plugin first.
• Pipeline: Groovy v2.23
  • Pipeline: Supporting APIs v2.9 failed to load. Fix this plugin first.
• Pipeline: Supporting APIs v2.11
  • Script Security Plugin v1.17 is older than required. To fix, install v1.21 or later.
• Pipeline: Multibranch v2.8
  • Folders Plugin v5.10 failed to load. Fix this plugin first.
• Pipeline: REST API Plugin v2.3
  • Pipeline: Supporting APIs v2.1 failed to load. Fix this plugin first.
• Jenkins Git plugin v3.0.1
  • Credentials Plugin v1.25 is older than required. To fix, install v2.1.8 or later.
  • Jenkins Git client plugin v2.1.0 failed to load. Fix this plugin first.
• Pipeline: Nodes and Processes v2.5
  • Pipeline: Supporting APIs v2.1 failed to load. Fix this plugin first.
• GitHub Authentication plugin v0.24
  • Jenkins Git plugin v2.0.3 failed to load. Fix this plugin first.
• Jenkins Git client plugin v2.1.0
  • SSH Credentials Plugin v1.11 is older than required. To fix, install v1.12 or later.
• Folders Plugin v5.12
  • Credentials Plugin v1.25 is older than required. To fix, install v2.0.4 or later.
• Pipeline: Input Step v2.5
  • Pipeline: Supporting APIs v2.10 failed to load. Fix this plugin first.
• Branch API Plugin v1.10
  • Folders Plugin v5.10 failed to load. Fix this plugin first.
• Pipeline: Job v2.9
  • Pipeline: Supporting APIs v2.2 failed to load. Fix this plugin first.
• Jenkins GIT server Plugin v1.7
  • Jenkins Git client plugin v1.11.0 failed to load. Fix this plugin first.

In which order should these be installed? 

For example I try to start with upgrading

• Credentials Plugin v1.25 is older than required. To fix, install v2.0.4 or later.

I restart Jenkins but it is still not installed.

[Daniel Beck]

Check the Jenkins log for more detailed error messages. They'll give you an idea what causes all of these plugins to fail to load. Often it's a cascading effect due to one or two broken/missing plugins.

I'm curious, how is this even possible? Do you manually manage your plugins/ directory?

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ef835b95-4615-486f-9323-69b552b82789%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Victor Martinez]

I had a kind of similar issues when I upgraded a few instances a few months ago, basically just upgrading those versions from the latest 1.X LTS to 2.7.3 , If I recall correctly. How did I fix it? I ordered those dependencies and installing them, a bit tedious but it worked fine.

I use Puppet to setup anything with the puppet-jenkins module, but unfortunately Jenkins plugins are a bit evil as their dependencies are not updated accordingly when using any Configuration Management tool.

I normally, export those jenkins instances setup using some groovy script to generate a local docker instance and then upgrade there, so if it works then i can almost 100% be confident my rollback will work as expected. 

Cheers

[Daniel Beck]

> On 26.11.2016, at 00:05, Victor Martinez <victormar...@gmail.com> wrote:
>
> unfortunately Jenkins plugins are a bit evil as their dependencies are not updated accordingly when using any Configuration Management tool

Good point. I think it depends on how these tools implement plugin installation. IIRC the CLI command can be terrible in "URL" mode, as is modifying plugins/ directly.

That said, dependency resolution in Jenkins just installs whatever is the newest version, which I'm pretty sure you don't want either -- so there's little that Jenkins can do.

Or can it? How would this need to work to be less problematic, with the caveat that Jenkins update sites will not be able to serve a list of plugin versions for the foreseeable future, and only offer the newest ones (and therefore will only install newest versions when resolving dependencies)?

Note that all regular dependency metadata is stored in the plugin ZIP file, so I'm kind of surprised config management tools haven't gotten this worked out. Sure, it's not as easy as just wrapping a one-line CLI command, but it's not an unsurmountable challenge. What am I missing?

[Anders Persson]

I found out the problem. I looked in the logfile and found rows like this

INFO: Ignoring C:\Users\Ulf\.jenkins\plugins\credentials (2).jpi because C:\Users\Ulf\.jenkins\plugins\credentials (1).jpi is already loaded
nov 25, 2016 9:16:09 EM hudson.PluginManager$1$3$1 isDuplicate
INFO: Ignoring C:\Users\Ulf\.jenkins\plugins\credentials.jpi because C:\Users\Ulf\.jenkins\plugins\credentials (1).jpi is already loaded

I looked in the plugins folder and all the plugins that I had problems with had versions like the one above. I removed the

credentials (1).jpl

and then I got the latest versin of the plugin loaded. So that explains why I did not get the new version of the credential plugin. Why this happen I do not know but I guess it is something with backup of the old version of the plugin that created the (1) version of the plugin and then the loading of the plugin unfortunately loaded the wrong version.

When that was done it was simple to upgrade the remaining plugins to the correct version.

[Daniel Beck]

> On 26.11.2016, at 21:49, Anders Persson <ander...@gmail.com> wrote:
>
> I guess it is something with backup of the old version of the plugin that created the (1) version of the plugin and then the loading of the plugin unfortunately loaded the wrong version.

Jenkins created plugin backup files are named .bak; this looks like backup copies manually created in-place, which clearly doesn't work. Don't do that.