-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Linux 2.6.31-19-server #56-Ubuntu SMP Thu Jan 28 03:40:48 UTC 2010 x86_64 GNU/Linux
We have a setup where the user is not hudson (default) but build:
Extract from /etc/default/hudson
# user id to be invoked as (otherwise will run as root; not wise!) HUDSON_USER=build
After hudson package upgrade (aptitude) I noticed that the permission in the following directory is set to hudson:adm again instead of ${HUDSON_USER}:
/var/lib/hudson <- hudson configuration
/var/run/hudson/war <- web root
This causes hudson to not run properly.
The user permissions should be changed to the user specified in HUDSON_USER.
Possible fix in /trunk/hudson/main/debian/hudson.postinst:
- Read HUDSON_USER from /etc/default/hudson or maybe hudson.default and set the permission accordingly
I'm not sure how to handle the group permission. It could be fixed to adm (current solution) or a new environment variable HUDSON_GROUP could be added.
A completely different approach could be to don't touch permission after upgrade at all.
A recent change in this area (JENKINS-4047) leaves the jobs directory untouched. But this doesn't fix the current problem.
- is related to
-
JENKINS-7575 .deb package postinst prevents serving static content directly
-
- Closed
-
[JENKINS-5771] Debian package upgrade sets wrong user permissions if HUDSON_USER is not hudson (default)
Link |
New:
This issue is related to |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 135863 ] | New: JNJira + In-Review [ 187062 ] |