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

Add an option for node label plugin that allows a job to be run explicitly on all hosts concurrently

XMLWordPrintable

      Currently, there is support for concurrent builds across multiple nodes, which allows you to select all available nodes as the default parameter list. This is great, providing the list of nodes doesn't change. It would be nice to have an option to explicitly say that you want the job to run concurrently on all hosts, which will be determined dynamically.

      For example, I want to update build tools in a common directory on all nodes when the job that builds the build tools detects a change in SCM and rebuilds them. I want this to work for new nodes that join the build pool, without explicitly requiring manual intervention.

      The only way to achieve this currently, is to create a job that runs on the master and modifies the Jenkins configuration for NodeLabel, to add any new found hosts to the static configuration, then restart Jenkins. Modifying the configuration isn't a major issue, but having to restart Jenkins is quite disruptive.

            domi Dominik Bartholdi
            iwonbigbro Craig Phillips
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: