-
Bug
-
Resolution: Postponed
-
Major
-
Jenkins ver. 1.595
MultiJob ver. 1.16
$ java -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr8-20141026_01(SR8))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20141013_217026 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR8_20141013_1240_B217026
JIT - r11_20141003_74578
GC - R26_Java726_SR8_20141013_1240_B217026_CMPRSS
J9CL - 20141013_217026)
JCL - 20141004_02 based on Oracle 7u71-b13
Red Hat Enterprise Linux Server release 5.11 (Tikanga)Jenkins ver. 1.595 MultiJob ver. 1.16 $ java -version java version "1.7.0" Java(TM) SE Runtime Environment (build pxa6470sr8-20141026_01(SR8)) IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20141013_217026 (JIT enabled, AOT enabled) J9VM - R26_Java726_SR8_20141013_1240_B217026 JIT - r11_20141003_74578 GC - R26_Java726_SR8_20141013_1240_B217026_CMPRSS J9CL - 20141013_217026) JCL - 20141004_02 based on Oracle 7u71-b13 Red Hat Enterprise Linux Server release 5.11 (Tikanga)
The MultiJob plugin continues to the next phase even though it's configured to continue only if all job statuses are successful. This occurred after a few builds showing the correct behavior.
