|
||||||||
|
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.
I found this issue quite frustrating. After wasting time wondering why my Powershell script worked if I ran it manually but not if it ran through Jenkins, I eventually came across this issue and determined the root cause. Yes, the issue may be listed as minor, but the considering headaches that it causes, it would seem to be worth the presumably minimal effort to fix this. My workaround was similar to what others have mentioned in manually fixing the path at the top of my script. Since I'm working with a Powershell script, here's the code I've got at the very top of my script to fix the problem:
$env:PATH = $env:PATH -replace '"', ""