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

Changes to slave environment variables are ignored by master

    XMLWordPrintable

Details

    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

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-27928 environment variable changes are not applied.

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-28278 Environment variables "stuck" on windows slave

          • Major - Major loss of function.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-69821 Changes to "built-in" environment variables are ignored always

          • Major - Major loss of function.
          • Open
          links to

          Web Link PR 1728

          Activity

            Ascending order - Click to sort in descending order
            View 46 older comments
            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

            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
            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.

            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.
            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    

             

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

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

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

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

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

            People

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

              Dates

                Created:
                Updated: