> On 26.11.2016, at 21:49, Anders Persson 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 .b
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:\U
> On 26.11.2016, at 00:05, Victor Martinez
> 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
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 t
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?
>
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
