|
||||||||
|
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)

I'm sorry for not getting back to you sooner.
>From an Unix environment, I can't reproduce the problem.
Could you attach your job configuration file, maybe I missed something.
More information
1) EnvInject plugin distinguishes PATH from Path from Windows because it is written in Java and I don't take in consideration of that at the moment.
2) If you don't use EnvInject, nothing is modified.
It is not intrusive.
Therefore, I don't understand your remark