Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-68944

Matrix jobs do not start with custom label/expression for the built-in node


    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • matrix-project-plugin
    • 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.

            Unassigned Unassigned
            capf Carsten Pfeiffer
            0 Vote for this issue
            3 Start watching this issue