-
Bug
-
Resolution: Fixed
-
Major
The jenkins-1.565-1.1 RPM contains a post-install script with performs the following:
# Ensure the right ownership on files . /etc/sysconfig/jenkins chown -R ${JENKINS_USER:-jenkins} /var/log/jenkins chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
These chowns can take a very long time on systems with lots of files. A couple of our Jenkins boxes have thousands of files in a the /var/lib/jenkins/workspace directory (which itself is a network mount), which means this chown takes many minutes to complete (like ~15 minutes) and actually changes the ownership of no files. This holds up package deployment unnecessarily.
I propose that either these chowns be removed entirely (the RPM spec sets the ownership of things the RPM puts down), or better yet that they're restricted to specific files.
- is related to
-
JENKINS-12231 RPM upgrade does not honor JENKINS_USER, and always resets files ownership to "jenkins"
-
- Resolved
-
-
JENKINS-26460 RPM upgrade/install should adapt ownership of /var/cache/jenkins
-
- Resolved
-
- links to
[JENKINS-23273] RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Description |
Original:
The jenkins-1.565-1.1 RPM contains a post-install script with performs the following: # Ensure the right ownership on files . /etc/sysconfig/jenkins chown -R ${JENKINS_USER:-jenkins} /var/log/jenkins chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins} These chowns can take a very long time on systems with lots of files. A couple of our Jenkins boxes have thousands of files in a the /var/lib/jenkins/workspace directory (which itself is a network mount), which means this chown takes many minutes to complete (like ~15 minutes). This holds up package deployment unnecessarily. I propose that either these chowns be removed entirely (the RPM spec sets the ownership of things the RPM puts down), or better yet that they're restricted to specific files. |
New:
The jenkins-1.565-1.1 RPM contains a post-install script with performs the following: {quote}{noformat} # Ensure the right ownership on files . /etc/sysconfig/jenkins chown -R ${JENKINS_USER:-jenkins} /var/log/jenkins chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins} {noformat}{quote} These chowns can take a very long time on systems with lots of files. A couple of our Jenkins boxes have thousands of files in a the /var/lib/jenkins/workspace directory (which itself is a network mount), which means this chown takes many minutes to complete (like ~15 minutes) and actually changes the ownership of no files. This holds up package deployment unnecessarily. I propose that either these chowns be removed entirely (the RPM spec sets the ownership of things the RPM puts down), or better yet that they're restricted to specific files. |
Assignee | New: Nicolas De Loof [ ndeloof ] |
Link |
New:
This issue is related to |
Summary | Original: RPM post-install should not do a "chown -R jenkins:jenkins /var/lib/jenkins" | New: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}" |
Labels | Original: rpm yum | New: regression rpm yum |
Link |
New:
This issue is related to |
Component/s | New: packaging [ 20120 ] | |
Component/s | Original: core [ 15593 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Assignee | Original: Nicolas De Loof [ ndeloof ] | New: Daniel Beck [ danielbeck ] |