-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
The InjectedTest PluginAutomaticTestBuilder$OtherTests.testPluginActive fails for the analysis-core plugin (branch 3.0) due to the following problem:
Caused by: java.io.IOException: Matrix Project Plugin v1.13 failed to load. - JUnit Plugin v1.6 is older than required. To fix, install v1.20 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626) at hudson.PluginManager$2$1$1.run(PluginManager.java:516) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1090) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) ... 3 more
However, if I start an IntegrationTest that uses the Matrix Plug-in, then the tests succeeds. I.e. Jenkins can load the Plug-in.
[INFO] Running io.jenkins.plugins.analysis.warnings.legacy.MatrixJobITest === Starting shouldCreateIndividualAxisResults(io.jenkins.plugins.analysis.warnings.legacy.MatrixJobITest) 0.052 [id=90] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: Running on http://localhost:60113/jenkins/ 0.164 [id=96] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 0.166 [id=100] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 0.633 [id=100] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 0.634 [id=96] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 0.637 [id=96] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 2.391 [id=101] WARNING i.j.p.a.w.FindBugsMessages#loadMessages: The bug pattern DM_INVALID_MIN_MAX was already loaded. It could be a duplicate. 2.804 [id=101] WARNING i.j.p.a.w.FindBugsMessages#loadMessages: The bug pattern DM_INVALID_MIN_MAX was already loaded. It could be a duplicate. 3.119 [id=99] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 3.123 [id=96] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 3.321 [id=105] INFO hudson.model.Run#execute: test0/user_axis=two #1 main build action completed: SUCCESS 3.321 [id=104] INFO hudson.model.Run#execute: test0/user_axis=one #1 main build action completed: SUCCESS 3.586 [id=131] INFO hudson.model.Run#execute: test0/user_axis=three #1 main build action completed: SUCCESS 4.233 [id=119] INFO hudson.model.Run#execute: test0 #1 main build action completed: SUCCESS 4.281 [id=90] INFO jenkins.model.Jenkins#cleanUp: Stopping Jenkins WARN: The method class org.apache.commons.logging.impl.SLF4JLogFactory#release() was invoked. WARN: Please see http://www.slf4j.org/codes.html#release for an explanation. 4.312 [id=90] INFO jenkins.model.Jenkins#cleanUp: Jenkins stopped [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.525 s - in io.jenkins.plugins.analysis.warnings.legacy.MatrixJobITest
The interesting thing is, that my integration test also complains in the console that the matrix plugin can't be loaded:
9.108 [id=21] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Matrix Project Plugin v1.13 (matrix-project) java.io.IOException: Matrix Project Plugin v1.13 failed to load. - JUnit Plugin v1.6 is older than required. To fix, install v1.20 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626) at hudson.PluginManager$2$1$1.run(PluginManager.java:516) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1090) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
However, this seem not to influence the test. And the test definitely requires the matrix plug-in.
I am using the latest versions of the parent pom. It is just impossible to fix all those plugin X depends on plugin Y warnings.
(See also mailing list thread)