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

OFFLINE_NODE_WHEN_COMPLETE not recognized on manual rebuild leaving node online

    Details

    • Similar Issues:

      Description

      When a job is triggered with additional parameters injected by the german-plugin, the rebuild-plugin does not populate them on rebuild.

      The Wikimedia setup has Zuul/Nodepool/Gearman-plugin. A parameter OFFLINE_NODE_WHEN_COMPLETE is set when the build is triggered via the gearman-plugin. It does not exist in the list of the jobs parameter but the build does show it up being set properly.

      When hitting [rebuild], previous parameters that are defined in the job configuration are populated from the previous build but the parameter OFFLINE_NODE_WHEN_COMPLETE that got injected is not.

        Attachments

          Activity

          Hide
          hashar Antoine Musso added a comment - - edited

          Might be the same as:

          Seems to be a regression from 1.22. Possibly introduced by the fix for JENKINS-20288

          Show
          hashar Antoine Musso added a comment - - edited Might be the same as: JENKINS-29671 JENKINS-27340 Seems to be a regression from 1.22. Possibly introduced by the fix for JENKINS-20288
          Hide
          hashar Antoine Musso added a comment -

          The Gearman plugin does not recognize the build parameters OFFLINE_NODE_WHEN_COMPLETE unless it is passed as a parameter to the gearman function (i.e. it does not work with rebuild).

          A workaround is to use the Single Use Slave Plugin https://wiki.jenkins-ci.org/display/JENKINS/Single+Use+Slave+Plugin , the plugin is given a list of labels to monitor, when a build is complete it will put the node offline regardless of OFFLINE_NODE_WHEN_COMPLETE

          Show
          hashar Antoine Musso added a comment - The Gearman plugin does not recognize the build parameters OFFLINE_NODE_WHEN_COMPLETE unless it is passed as a parameter to the gearman function (i.e. it does not work with rebuild). A workaround is to use the Single Use Slave Plugin https://wiki.jenkins-ci.org/display/JENKINS/Single+Use+Slave+Plugin , the plugin is given a list of labels to monitor, when a build is complete it will put the node offline regardless of OFFLINE_NODE_WHEN_COMPLETE

            People

            • Assignee:
              ragesh_nair ragesh_nair
              Reporter:
              hashar Antoine Musso
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: