mirror of
https://github.com/jenkinsci/jenkins.git
synced 2026-11-07 00:55:59 +00:00
Kohsuke Kawaguchi
2218754197
ahochsteger asks 'why do we mess with file permissions anyway?' and he's right! I digged the history but couldn't find why we do it. I think we should just set the permissions of the top-level directories, but leave the other file permissions as-is. In addition, - I see no point in touching usr/bin usr/sbin. perhaps C&P mistake from some samples? - Don't touch /var/lib/hudson if .for-jenkins is present, so that people using the hudson user can keep upgrading new versions of jenkins and run it as hudson - /var/run/hudson contains no important information, so no need to bring it over to /var/run/jenkins
14 lines
500 B
Plaintext
14 lines
500 B
Plaintext
# moved from rules install
|
|
usr/share/jenkins
|
|
|
|
# this is where JENKINS_HOME is stored, so let's leave it as is for now
|
|
var/lib/jenkins
|
|
|
|
# Need to create jenkins's own directory to track the pid since the daemon is not run as root
|
|
# and doesn't have permission to write the pid to /var/run (which would be the preferred location).
|
|
var/run/jenkins
|
|
|
|
# Store jenkins log file in it's own directory since they can become rather large and in the future
|
|
# rotating logs can be easily added.
|
|
var/log/jenkins
|