-
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.
[JENKINS-68944] Matrix jobs do not start with custom label/expression for the built-in node
Carsten Pfeiffer
created issue -
Carsten Pfeiffer
made changes -
| Description |
Original:
Matrix jobs only start when using exactly the {{built-in}} label to select a 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. |
New:
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. |
| Component/s | New: core [ 15593 ] |
| Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] |
| Component/s | Original: core [ 15593 ] |
| Summary | Original: Matrix jobs do not start with custom label/exprssion for the built-in node | New: Matrix jobs do not start with custom label/expression for the built-in node |
| Attachment | New: image-2022-07-08-00-17-43-563.png [ 58440 ] |