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

Changes to slave environment variables are ignored by master

      A slave's environment variables seem to be cached upon first connect and then never considered again. This prevents legitimate changes to a slave's environment from having any effect on builds. The only workaround I can find is to delete a slave and recreate it, which in a complex environment is unacceptable.

      This may be a consequence of JENKINS-26755.

          [JENKINS-27739] Changes to slave environment variables are ignored by master

          Daniel Beck added a comment -

          still persists on my 1.606 instance

          This is to be expected, as this issue was fixed in 1.617.

          Daniel Beck added a comment - still persists on my 1.606 instance This is to be expected, as this issue was fixed in 1.617.

          Baptiste Mathus added a comment - - edited

          FWIW, (very) similar issue seen on Jenkins 1.625.2. PATH was modified in the agent /configure, but wasn't taken in account until disconnecting/reconnecting the agent. Other variables were immediately propagated.

          Not sure I'll have time to get the bottom of it in the next few days to file a complete new issue, but in case someone comes here, maybe that'll help.

          EnvInject 1.92.1.

          Agent connected using ssh-slaves 1.10. IBM AIX agent.

          Baptiste Mathus added a comment - - edited FWIW, (very) similar issue seen on Jenkins 1.625.2. PATH was modified in the agent /configure, but wasn't taken in account until disconnecting/reconnecting the agent. Other variables were immediately propagated. Not sure I'll have time to get the bottom of it in the next few days to file a complete new issue, but in case someone comes here, maybe that'll help. EnvInject 1.92.1. Agent connected using ssh-slaves 1.10. IBM AIX agent.

          Kobi Hakimi added a comment -

          I updated environment variable but didn't see the updated value just after disconnect and reconnect the agent.

          We use Jenkins 1.656

          Kobi Hakimi added a comment - I updated environment variable but didn't see the updated value just after disconnect and reconnect the agent. We use Jenkins 1.656

          Nehal J Wani added a comment -

          Please note that bringing the slave online/offline doesn't help. One has to disconnect the slave and relaunch the slave agent. This worked for me for Jenkins version: 1.651.2

          Nehal J Wani added a comment - Please note that bringing the slave online/offline doesn't help. One has to disconnect the slave and relaunch the slave agent. This worked for me for Jenkins version: 1.651.2

          Hello,

          Same as Nehal, I have the problem with Jenkins 1.651.1.

          Paris BP2S CI Project added a comment - Hello, Same as Nehal, I have the problem with Jenkins 1.651.1.

          Mathew Joseph added a comment -

          Am seeing this behaviour with Jenkins 2.46.3 

          Does not disappear even if slave is disconnected and reconnected

          Does not go if slave is deleted and reset with a different name

          Mathew Joseph added a comment - Am seeing this behaviour with Jenkins 2.46.3  Does not disappear even if slave is disconnected and reconnected Does not go if slave is deleted and reset with a different name

          Oleg Nenashev added a comment -

          If somebody hits this issue, please consider reopening it or creating a new one. The latter may be preferable from the triaging perspective.

          Oleg Nenashev added a comment - If somebody hits this issue, please consider reopening it or creating a new one. The latter may be preferable from the triaging perspective.

          There still this behavior, within Jenkins version Jenkins ver. 2.190.1

          I tried node deleting / creating, Jenkins restarting... Nothing helped    

           

          Nedeljko Markovic added a comment - There still this behavior, within Jenkins version  Jenkins ver. 2.190.1 I tried node deleting / creating, Jenkins restarting... Nothing helped      

          this issue still exist in the Jenkins version Jenkins ver. 2.190.1

          Nedeljko Markovic added a comment - this issue still exist in the Jenkins version  Jenkins ver. 2.190.1

          Hariharan added a comment -

          This issue persists on Jenkins 2.277.4. This requires restarting slaves whenever there is an update to path.

          Hariharan added a comment - This issue persists on Jenkins 2.277.4. This requires restarting slaves whenever there is an update to path.

            Unassigned Unassigned
            siggimoo Milo Hyson
            Votes:
            17 Vote for this issue
            Watchers:
            36 Start watching this issue

              Created:
              Updated: