[JIRA] [envinject] (JENKINS-23615) Unexpected behaviour when using different capitalization for variable name on windows

[andreas.la...@esi-group.com (JIRA)]

Andreas Kleber created JENKINS-23615 Unexpected behaviour when using different capitalization for variable name on windows Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 30/Jun/14 5:57 AM Description: On windows environment variable names an not case sensitive. If you use different capitalization in variable names with the envinject plugin the results are unexpected. To reproduce create a envinject build step or build environment setting with the following content: Foo=test FOO=bar;$FOO If I run the job on a windows slave I would expect the result to be: echo %FOO% bar;test But instead I get: echo %FOO% bar;bar;bar;bar;bar;bar;bar;bar;.........bar;bar;bar;$FOO On the "Environment Variables" page on the job result page there are two entries with the different capitalization but also not filled correctly. I would expect only one. I found out about this because on a freshly installed windows machine the Path environment variable is "Path" but I used "PATH" in the envinject plugin which gave me quite some headache. Project: Jenkins Priority: Critical Reporter: Andreas Kleber

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.