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

Matrix jobs tied to label executed consecutively even if there are free nodes of this label

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • matrix-project-plugin
    • None
    • WinXP, Hudson v.1.376, each node configured as "number of executors"=1

      0. Two nodes of label 'X32' configured as "number of executors"=1
      1. Create a "free-style software project", tie it to 'X32' label.
      Run this job twice - two builds will be run simultaneously, both nodes are used. It is OK.
      2. Create a "multi-configuration project", tie it to 'X32' label.
      Run this job twice - one build started and running, another job is in queue, only one node is used.

          [JENKINS-7542] Matrix jobs tied to label executed consecutively even if there are free nodes of this label

          bult added a comment -

          If matrix project tied to several labels and some of them are busy, I prefer to see job started before each label node become free.

          bult added a comment - If matrix project tied to several labels and some of them are busy, I prefer to see job started before each label node become free.

          I see the same thing. To have matrix builds distribute tests I need to specify the nodes individually - I can't use the label. All my nodes are also only single executors. My current Jenkins version is 1.420.

          Stephen Morrison added a comment - I see the same thing. To have matrix builds distribute tests I need to specify the nodes individually - I can't use the label. All my nodes are also only single executors. My current Jenkins version is 1.420.

            Unassigned Unassigned
            bult bult
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: