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

When triggered by timer, Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label.

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hello,

      I set up a job which is supposed to be build on all slave nodes sharing a label. I try to achieve this using the NodeLabel Parameter Plugin version 1.7.1.
      I selected "Run on all nodes matching the label", and "Run regardless of result".

      However, when I trigger the job by hand, it runs on all nodes matching the label. By when started by timmer, it only runs on a random node. The one node changes between iterations.

      I include screenshots of my setup as attachments. Jenkins version is 1.643.

        Attachments

          Issue Links

            Activity

            Show
            escoem Emilio Escobar added a comment - https://github.com/jenkinsci/nodelabelparameter-plugin/pull/11
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Emilio Escobar
            Path:
            src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/LabelParameterDefinition.java
            http://jenkins-ci.org/commit/nodelabelparameter-plugin/dab454fd17cbd371aa78791e191f224c0874c3c0
            Log:
            JENKINS-32939 changed the constructor when asking for default value.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Emilio Escobar Path: src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/LabelParameterDefinition.java http://jenkins-ci.org/commit/nodelabelparameter-plugin/dab454fd17cbd371aa78791e191f224c0874c3c0 Log: JENKINS-32939 changed the constructor when asking for default value.
            Hide
            mikz Michal Cichra added a comment -

            This is not fixed for me in 1.7.2. Downgrading back to 1.6 from 1.7 series does the trick.

            Even building by hand and selecting all nodes runs it only on the first one.

            Show
            mikz Michal Cichra added a comment - This is not fixed for me in 1.7.2. Downgrading back to 1.6 from 1.7 series does the trick. Even building by hand and selecting all nodes runs it only on the first one.

              People

              Assignee:
              escoem Emilio Escobar
              Reporter:
              liangbo Bo Liang
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated: