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

Changes to slave environment variables are ignored by master

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            paris_bp2s_ci_project Paris BP2S CI Project added a comment -

            Hello,

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

            Show
            paris_bp2s_ci_project Paris BP2S CI Project added a comment - Hello, Same as Nehal, I have the problem with Jenkins 1.651.1.
            Hide
            cryptomatt 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

            Show
            cryptomatt 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
            Hide
            oleg_nenashev 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.

            Show
            oleg_nenashev 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.
            Hide
            markoned 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    

             

            Show
            markoned 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      
            Hide
            markoned Nedeljko Markovic added a comment -

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

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

              People

              • Assignee:
                Unassigned
                Reporter:
                siggimoo Milo Hyson
              • Votes:
                12 Vote for this issue
                Watchers:
                32 Start watching this issue

                Dates

                • Created:
                  Updated: