|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14569) PATH is not bein... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... [email protected] (JIRA)

Additional side effect: on a Windows slave there is predefined environment variable named Path. When setting PATH=C:\Program Files\7-Zip;${PATH} as EnvInject setup, it results in both PATH and Path injected variables, where Path is original (without 7-Zip) and PATH contains 7-Zip. Anyway, the build later fails since apparently Windows checks Path and not PATH (or probably these two count as one and it depends on what order they are set).
As a workaround I have corrected EnvInject setup to set Path not PATH and it works. However, standard environment setup feature from Jenkins did not work this way, i.e. correctly expanded Path with the same setup as above (PATH=C:\Program Files\7-Zip;${PATH})