[JIRA] (JENKINS-16255) Jenkins doesn't handle system wide environment variables which exist in different cases

[hsku...@gmail.com (JIRA)]

Henrik Skupin created JENKINS-16255 Jenkins doesn't handle system wide environment variables which exist in different cases Issue Type: Bug Affects Versions: current Assignee: Jørgen Tjernø Components: environment-script Created: 03/Jan/13 5:11 PM Description: 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. Environment: Ubuntu 12.04 x86 Project: Jenkins Priority: Major Reporter: Henrik Skupin

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira