-
Bug
-
Resolution: Unresolved
-
Critical
-
OS:Window XP
jenkins :1.4.8
build-pipeline:1.3.4-SNAPSHOT
I use the build-pipeline source code to make a newly builds.
After I install the new build into jenkins ,it give a java.io.IOException.
java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist
at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479)
at hudson.PluginManager$2$1$1.run(PluginManager.java:332)
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:883)
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(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
om.thoughtworks.xstream.mapper.CannotResolveClassException: au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView : au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView
at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68)
at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
you can find more detail in the attach file.
I experienced this as well, both with the current code base as well as going back to the 1.3.3 time frame with 34c17d66dc3fae5cdd52efb387e4ae1e97a040d2. However, I found that if I removed the old plugin folder and the build-pipeline-plugin.jpi file, copied the new build-pipeline-plugin.hpi to the plugins folder, renamed as a jpi file. It deployed successfully. I don't know which of these steps were the 'fix'. Actually, this did not work for the current head.