is not called by Jenkins.
PluginImpl is supposed to be initialized by Jenkins because PluginImpl extends Plugin.
How to reproduce the issue?
And what version of Jenkins was used?
evernat added a comment - 2016-05-13 16:03 It seems that either Jenkins.getInstance().getPlugin(org.jvnet.hudson.plugins.monitoring.PluginImpl.class) returns null or PluginImpl.start() is not called by Jenkins. PluginImpl is supposed to be initialized by Jenkins because PluginImpl extends Plugin. How to reproduce the issue? And what version of Jenkins was used?
Unfortunately, it looks like it is a transient issue - so I don't know how to re-produce it.
You are right. I am updating the PR right now.
Félix Belzunce Arcos added a comment - 2016-05-18 18:45 Unfortunately, it looks like it is a transient issue - so I don't know how to re-produce it. You are right. I am updating the PR right now. Thanks for your feedback!
Last night we updated to Jenkins 2.9 from 2.8 and also the monitoring plugin was updated from 1.57 to 1.59. We are no experiencing this issue and had to downgrade the plugin. When will this be released as it is marked as resolved.
Bruce Coveny added a comment - 2016-06-14 11:58 Last night we updated to Jenkins 2.9 from 2.8 and also the monitoring plugin was updated from 1.57 to 1.59. We are no experiencing this issue and had to downgrade the plugin. When will this be released as it is marked as resolved.
In fact, it was released just 2 hours before you ask.
The plugin should be available in your update center now or in 24h.
evernat added a comment - 2016-06-14 17:36 Hi Bruce, In fact, it was released just 2 hours before you ask. The plugin should be available in your update center now or in 24h.