-
Bug
-
Resolution: Fixed
-
Major
-
None
While plugins are started in the correct order when deployed normally (and via hpi:run), the upstream plugin is not started before the dependent plugin when run under HudsonTestCase.
Steps to reproduce:
git clone git://github.com/recampbell/jenkins-plugin-bugs.git
cd jenkins-plugin-bugs/JENKINS-9960
mvn clean install
[JENKINS-9960] Plugin Dependencies not started before plugin in HudsonTestCase
URL | New: https://github.com/recampbell/jenkins-plugin-bugs/tree/master/JENKINS-9960 | |
Description |
Original:
While plugins are started in the correct order when deployed normally (and via hpi:run), the upstream plugin is not started before the dependent plugin when run under HudsonTestCase. |
New:
While plugins are started in the correct order when deployed normally (and via hpi:run), the upstream plugin is not started before the dependent plugin when run under HudsonTestCase. Steps to reproduce: git clone git://github.com/recampbell/jenkins-plugin-bugs.git cd jenkins-plugin-bugs/ mvn clean install |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 140148 ] | New: JNJira + In-Review [ 188870 ] |
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/src/main/java/hudson/PluginManager.java
core/src/main/java/hudson/util/CyclicGraphDetector.java
plugins/pom.xml
pom.xml
http://jenkins-ci.org/commit/jenkins/e03ba7dc6ba3753ed18d0de02133734ab171fb21
Log:
[FIXED JENKINS-9960]
We weren't actually enforcing the initialization order at all, as
sorting was based on the plugin name.
Compare: https://github.com/jenkinsci/jenkins/compare/938ac77...e03ba7d