-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Windows
I have a top level job X. In X, I am using kicking off job Y using the File Parameter Factory option in parameterized builds. The configuration files contain a property, axis_values, which is a space separated list of different axis's for job Y.
Let's say that job X has one configuration file and it contains axis_values=A B C. I kick off job X, which in turn kicks one instance of job Y. Job Y iterates correctly through A, B and C.
Next, I change the configuration file and I set axis_values=A B C D E. I kick off job X and job Y starts. Job Y runs correctly for A, B and C. But, job Y fails to run D and E. It says that "D appears to be cancelled" and "E appears to be cancelled".
I see the following in the log:
31-May-2013 3:57:48 PM hudson.model.Executor run
SEVERE: Executor threw an exception
java.lang.NullPointerException
at hudson.model.Executor.run(Executor.java:238)
The only workaround that I have found is that it will work correctly if I put the new values at the start of the axis. (ie. axis_values=D E A B C)
List of (possibly) relevant plugins installed;
- dynamic axis
- environment injector
- jenkins parameterized trigger
- matrix sorter
- node and label parameter plugin
- is related to
-
JENKINS-24110 NPE in hudson.model.Executor when a task creates null Executable
-
- Resolved
-
-
JENKINS-19179 Matrix sub-jobs get disabled
-
- Resolved
-
[JENKINS-18164] Matrix Jobs Do Not Get Run When Updating a Dynamic Axis
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Link |
New:
This issue is related to |
Component/s | New: matrix-project [ 18765 ] | |
Component/s | Original: matrix [ 15501 ] |
Link |
New:
This issue is related to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 149462 ] | New: JNJira + In-Review [ 193137 ] |