-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.518
I have seen matrix sub-jobs abort before even starting a build on a slave machine. On investigating further I see that for some reason the sub-job config.xml files contain the tags:
<disabled>true</disabled>
even though the matrix job is enabled and indeed the top level config.xml contains:
<disabled>false</disabled>
This seems to happen to jobs that have been copied from other matrix jobs where the axis configurations have changed a few times.
Since the user has no control over this tag it must be redundant. I think that the code should force the disabled tag to be false for all child jobs.
- is related to
-
JENKINS-18164 Matrix Jobs Do Not Get Run When Updating a Dynamic Axis
- Resolved
-
JENKINS-24341 Subversion disables projects, which do not support the disabling
- Resolved
-
JENKINS-24340 AbstractProject: makeDisabled() performs operations even if supportsMakeDisabled() is false
- Resolved