-
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 ] |
I can't duplicate the problem as reported. I've been using built-in || master as a job label for quite a while with good results. Can you provide more details that will help others understand how you are seeing the issue?
Steps I took to try to duplicate the issue:
- Run a Jenkins 2.346.1 controller with matrix project plugin 772.v494f19991984 as described in my lts-with-plugins branch
- Add agents to the controller, set the agent executor count on the controller to zero
- Define a matrix project job with the label built-in || master and confirm that it starts but does not complete so long as executor count on the controller is zero
- Change controller executor count to 1, confirm that the job runs on the controller
| 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 |
The problem occurs when you configure label built-in || master for matrix project (parent job) itself and not for axis.
<?xml version="1.1" encoding="UTF-8" standalone="no"?> <matrix-project plugin="matrix-project@771.v574584b_39e60"> ... <assignedNode>built-in || master</assignedNode> <canRoam>false</canRoam> ... </matrix-project>
| Attachment | New: image-2022-07-08-00-17-43-563.png [ 58440 ] |
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