|
||||||||
|
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.
As a workaround...
We actually mount a filesystem on `/var/lib/jenkins` and umount it when doing updates. This actually happens because we upgrade jenkins on the inactive cluster node, but maybe its an option for others.
I still vote for only running chown if the JENKINS_USER is not "jenkins". If someone is "changing" from a non standard user to jenkins, then its on them to deal with the chown themselves. Quite frankly, anyone using a non-standard user to run jenkins while trying to use RPM jenkins and the "rpm provided" directories deserve what trouble they have.![]()
~tommy