|
||||||||
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... ra...@java.net (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... ra...@java.net (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... ra...@java.net (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... ra...@java.net (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... ra...@java.net (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... ra...@java.net (JIRA)
- [JIRA] (JENKINS-14569) PATH is not... ra...@java.net (JIRA)
I have verified on a clean Jenkins installation that it works correctly indeed. It seems that there is some conflict with "Hudson setenv plugin". It was installed so long ago that I didn't remember it was a plugin; thought that setting environment was a Jenkins built-in. Clean Jenkins installation convinced me it's not.
Anyway, seems not to be a problem. Rather my configuration issue.