Jenkins doesn't handle system wide environment variables which exist in different cases

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      If system-wide environment variables have been set via /etc/environment those are not accessible if they exist in lower-case and capital case letters. Jenkins combines both variables into a single one, and updates the first detected variable with the value of the second one. Here some examples:

      Example 1:

      /etc/environment
      http_proxy=http://proxy.dmz.example.org:8080
      HTTP_PROXY=http://proxy.dmz.example.org:8080

      -> Jenkins:
      HTTP_PROXY=http://proxy.dmz.example.org:8080

      Example 2:

      Shell:
      export test=1
      export TEST=2

      -> Jenkins
      TEST=1

      Jenkins should not modify set environment variables because it will cause problems with tools which rely on the right capitalization. One example is mercurial which needs the lower case version of the proxy configuration. It will no longer work when both variables are set.

            Assignee:
            Unassigned
            Reporter:
            Henrik Skupin
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: