Changes to slave environment variables are ignored by master

XMLWordPrintable

      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.

        1. support.zip
          2.06 MB

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

              Created:
              Updated: