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

            People

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

              Dates

                Created:
                Updated: