|
||||||||
|
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/groups/opt_out.
You were correct. I installed a fresh vanilla jenkins 1.500 + latest perforce plugin. There were no such problems exposing P4CLIENT to the env. But after installing envinject (which we have by default on our own customized jenkins war) the problem was visible. Any idea can this be fixed on perforce plugin at all? Or should we go directly to envinject plugin?