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

Not running the job on all slaves in Label parameter

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I have assigned 5 slaves with the same label name (EX: dev_sev). I want to run a job concurrently on all the 5 slaves using the label parameter. Within my job, I have created parameterized Label and set label value to (dev_sev). I have also selected the following options, "Run on all nodes matching the label", "Run regardless of result", Node eligibility: All nodes", and "Execute concurrent builds if necessary".

      When I execute the build, the label shows up and I can see all the 5 slaves show nodes, but the job is running on one of the nodes only. How do I resolve this issue with label param? I don't want to use a node parameter.

        Attachments

          Activity

          Hide
          cobexer Ing. Christoph Obexer added a comment -

          I can also reproduce this, back when we started to run the same job on multiple node simultaneously we also had this issue but I believe a coworker of mine got it working somehow.

          We switched to a Matrix Job with the Elastic Axis plug-in because of the much nicer visualization, maybe give that a try.

          Show
          cobexer Ing. Christoph Obexer added a comment - I can also reproduce this, back when we started to run the same job on multiple node simultaneously we also had this issue but I believe a coworker of mine got it working somehow. We switched to a Matrix Job with the Elastic Axis plug-in because of the much nicer visualization, maybe give that a try.
          Hide
          ahmedp Perwaize Ahmed added a comment -

          Thanks Chris. I tested it with Elastic Axis and it works. BTW, If you able to find out from your co-worker how they got the NodeLabel plugin to work, I would love to know.

          Now that I got the job running on multiple nodes simultaneously, I would like to prompt the user to enter the Label name. Here is why

          We have well over 2000+ slaves and I have grouped them into about 700 labels.

          I have created a job and would like to prompt the user to enter the label name. I want to pass that label name as a variable to the Elastic axis plugin and execute the project on those nodes.

          Thanks

          Show
          ahmedp Perwaize Ahmed added a comment - Thanks Chris. I tested it with Elastic Axis and it works. BTW, If you able to find out from your co-worker how they got the NodeLabel plugin to work, I would love to know. Now that I got the job running on multiple nodes simultaneously, I would like to prompt the user to enter the Label name. Here is why We have well over 2000+ slaves and I have grouped them into about 700 labels. I have created a job and would like to prompt the user to enter the label name. I want to pass that label name as a variable to the Elastic axis plugin and execute the project on those nodes. Thanks
          Hide
          cobexer Ing. Christoph Obexer added a comment -

          From what I could dig out of the job configuration history it seems we had 2 jobs, one which had the label parameter and another one that triggered it using Trigger / call build on other projects and an "All nodes for Label" parameter factory (my UI is in German, your labels may differ).

          HTH

          Show
          cobexer Ing. Christoph Obexer added a comment - From what I could dig out of the job configuration history it seems we had 2 jobs, one which had the label parameter and another one that triggered it using Trigger / call build on other projects and an "All nodes for Label" parameter factory (my UI is in German, your labels may differ). HTH

            People

            Assignee:
            domi Dominik Bartholdi
            Reporter:
            ahmedp Perwaize Ahmed
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: