|
||||||||
|
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.
Actually, it is related to the Jenkins working/home directory (see
JENKINS-18459) as this is where Jenkins usually is given read/write access.In an environment where Jenkins WAR is running inside an existing Tomcat application server with user 'tomcat7', Jenkins fails as the user does not have write access to the user's home directory (usually that's '/usr/share/tomcat7') for security reasons.
If the slave FS root solves this problem, that's perfect. Just make sure that the actual user running Jenkins has write access to this directory.