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

Node environment variable change not recognized

      When changing an existing node environment variable value in the node's configuration dialog, the change is not applied. Looking at the systemInfo of the node shows, that the variable still has got the old value. Also reloading the Jenkins configuration from disk did not help.

          [JENKINS-14801] Node environment variable change not recognized

          Workaround: a manual restart of the Jenkins Slave service is needed to update the variable.

          Christoph Jaehnigen added a comment - Workaround: a manual restart of the Jenkins Slave service is needed to update the variable.

          Daniel Beck added a comment -

          The updated value is supplied to builds, it's only the node system information page that's affected (on 1.561), so lowering priority.

          Daniel Beck added a comment - The updated value is supplied to builds, it's only the node system information page that's affected (on 1.561), so lowering priority.

          marlene cote added a comment -

          This affects builds for us please raise the priority.

          marlene cote added a comment - This affects builds for us please raise the priority.

          Please raise the priority of this issue as restarting the Jenkins Slave service does not resolve it. Wrong values are being passed to our build jobs.

          Jeff Skibinski added a comment - Please raise the priority of this issue as restarting the Jenkins Slave service does not resolve it. Wrong values are being passed to our build jobs.

          Daniel Beck added a comment -

          Are all of you using Jenkins 1.477? If not, more information would be helpful. It is really unlikely that you are experiencing this old issue when you get different symptoms.

          https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Read it. Seriously.

          Daniel Beck added a comment - Are all of you using Jenkins 1.477? If not, more information would be helpful. It is really unlikely that you are experiencing this old issue when you get different symptoms. https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Read it. Seriously.

          marlene cote added a comment -

          gosh, how embarrassing. So sorry I didn't notice the version. We are having the problem described in this defect report. We are using version 1.608.
          should I open a new issue?

          marlene cote added a comment - gosh, how embarrassing. So sorry I didn't notice the version. We are having the problem described in this defect report. We are using version 1.608. should I open a new issue?

          Daniel Beck added a comment -

          Yes, please file a new issue. Include the information requested in the wiki.

          Daniel Beck added a comment - Yes, please file a new issue. Include the information requested in the wiki.

          I encountered the same issue on version 1.608 - can you provide the link of the new bug?

          Aldrin Seychell added a comment - I encountered the same issue on version 1.608 - can you provide the link of the new bug?

          Daniel Beck added a comment - - edited

          FWIW the occurrence of a similar issue that was repeatedly mentioned above has been resolved in 1.617.

          Daniel Beck added a comment - - edited FWIW the occurrence of a similar issue that was repeatedly mentioned above has been resolved in 1.617.

          Mark Waite added a comment -

          Closing after an extended period with no response to the request for more information

          Mark Waite added a comment - Closing after an extended period with no response to the request for more information

            Unassigned Unassigned
            desolat Christoph Jaehnigen
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: