-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Linux
When setting different variables (HTTP_PROXY and http_proxy, for example), only the one that's listed first in the configuration file under "environmentVariables:" is actually set on the node (verified with a simple job that runs the "env" command from a shell step). If order is changed, the other one wins.
The expected behavior is that BOTH variables are set. Please fix.
[JENKINS-73475] environmentVariables: from configuration file are added case-insensitive, preventing variables with different casing from being set
Description |
Original:
When setting different variables (HTTP_PROXY and http_proxy, for example), only the on that's listed first in the configuration file under "environmentVariables:" is actually set on the node (verified with a simple job that runs the "env" command from a shell step). If order is changed, the other one wins.
The expected behavior is that BOTH variables are set. Please fix. |
New:
When setting different variables (HTTP_PROXY and http_proxy, for example), only the one that's listed first in the configuration file under "environmentVariables:" is actually set on the node (verified with a simple job that runs the "env" command from a shell step). If order is changed, the other one wins.
The expected behavior is that BOTH variables are set. Please fix. |