-
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
-
As noted in this Q&A the workaround is to browse to configure on the matrix configuration and uncheck Disabled.
Clearly one bug is that a matrix configuration got disabled somehow, i.e. the MatrixConfiguration.disabled field was set. How?
The next bug is that configure (and configSubmit) are even available on matrix configurations (albeit without a sidebar link), when there does not seem to be any intent for these config.xml files to be individually configurable. (The configure page shows all sorts of options, such as SCMs, which are definitely not supposed to be allowed on configurations.) These URLs should presumably be blocked. The config.xml URL is also available; in GET mode this might be OK, but a POST to it is probably also bad.
Then there is the problem that despite the fact that MatrixConfiguration.supportsMakeDisabled is false, so no UI button appears to explicitly enable or disable the project, isDisabled is not overridden to unconditionally return true.