search

zynxhealth / z-mon

a jenkins build monitor plugin
33 stars 24 forks source link

Jenkins ver. 1.514 compatibility #2

Closed lplotni closed 11 years ago

lplotni commented 11 years ago

Hi,

I cloned the repo, and build the hpi file (via mvn package) but I after an manual install jenkins is not listing the plugin as installed nor I can select zmon as display type for a the new view. Is it a version compatibility issue? I'm using 1.514

lplotni commented 11 years ago

Quick update: I analysed my jenkins log and found following stacktrace:

SEVERE: Failed Loading plugin z-mon java.io.IOException: Dependency claim (1.7) doesn't exist at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479) at hudson.PluginManager$2$1$1.run(PluginManager.java:333) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722)

abrooke commented 11 years ago

We haven't worked on that plugin in a very long time, it was specifically made for our environment.  No one is currently supporting it, so for now there is nothing I can say about it.

Thanks, Aslan Brooke

InfoQ | Blog | LinkedIn | Twitter | GitHub

From: Lukasz Plotnicki notifications@github.com To: zynxhealth/z-mon z-mon@noreply.github.com Sent: Thursday, May 23, 2013 2:37 AM Subject: Re: [z-mon] Jenkins ver. 1.514 compatibility (#2)

Quick update: I analysed my jenkins log and found following stacktrace: SEVERE: Failed Loading plugin z-mon java.io.IOException: Dependency claim (1.7) doesn't exist at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479) at hudson.PluginManager$2$1$1.run(PluginManager.java:333) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) — Reply to this email directly or view it on GitHub.

SteveMoyer commented 11 years ago

Just pushed a pom change with some updated dependencies which fix the problem