|
||||||||
|
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/d/optout.
Yes, that's the strange thing, I could run it from a cmd window.
However, seems to be a problem in Windows Server 2012, we've also seen these permission problems elsewhere. Recursively assigning "full control" for $JENKINS_HOME to the user running the slave solved the problem.