-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.346.1
matrix-project-plugin 771.v574584b_39e60 at least
Matrix jobs only start when specifying exactly built-in as label to select the built-in node.
When using a label expression like "built-in || master" or a different label that is configured for the built-in node, the matrix job will stay in the queue forever.
This used to work fine with Jenkins 2.264.3.
Note: the matrix jobs WILL start fine with a label or label expression that resolves e.g. to a docker cloud instead of the built-in node.
FYI: A matrix parent job is handled as flyweight task. The labels of the built-in node are ignored during the check whether the flyweight task is bound to the built-in node. Only self-label will be respected. See https://github.com/jenkinsci/jenkins/blob/jenkins-2.346.1/core/src/main/java/hudson/model/Queue.java#L1740