Skip to content
Browse files
[JENKINS-23273] Removed the hudson -> jenkins migration
It does not make sense nowadays, and if we remove that we do not need to
chown the jenkins installation folders because they are created with the proper user
  • Loading branch information
raul-arabaolaza committed Jan 16, 2017
1 parent 6cbcaf9 commit 5083f2ea1fbae613870cee96df1ce90f891b7202
Showing with 0 additions and 36 deletions.
  1. +0 −36 rpm/build/SPECS/jenkins.spec
@@ -79,42 +79,6 @@ rm -rf "%{buildroot}"
/sbin/chkconfig --add %{name}

# If we have an old hudson install, rename it to jenkins
if test -d /var/lib/hudson; then
# leave a marker to indicate this came from Hudson.
# could be useful down the road
# This also ensures that the .??* wildcard matches something
touch /var/lib/hudson/.moving-hudson
# remove the hudson default update site to prevent it to be used by jenkins
if test -e /var/lib/hudson/updates/default.json; then
rm /var/lib/hudson/updates/default.json
mv -f /var/lib/hudson/* /var/lib/hudson/.??* /var/lib/%{name}
rmdir /var/lib/hudson
find /var/lib/%{name} -user hudson -exec chown %{name} {} + || true
if test -d /var/run/hudson; then
mv -f /var/run/hudson/* /var/run/%{name}
rmdir /var/run/hudson

# Ensure the right ownership on files only if not owned by JENKINS_USER
. /etc/sysconfig/%{name}
if test x"$JENKINS_INSTALL_SKIP_CHOWN" != "xtrue"; then
owner=$(ls -ld /var/cache/%{name} | awk 'NR==1 {print $3}')
if [ "$owner" != "${JENKINS_USER:-%{name}}" ] ; then
chown -R ${JENKINS_USER:-%{name}} /var/cache/%{name}
owner=$(ls -ld /var/log/%{name} | awk 'NR==1 {print $3}')
if [ "$owner" != "${JENKINS_USER:-%{name}}" ] ; then
chown -R ${JENKINS_USER:-%{name}} /var/log/%{name}
owner=$(ls -ld ${JENKINS_HOME:-%{workdir}}| awk 'NR==1 {print $3}')
if [ "$owner" != "${JENKINS_USER:-%{name}}" ] ; then
chown -R ${JENKINS_USER:-%{name}} ${JENKINS_HOME:-%{workdir}}

if [ "$1" = 0 ] ; then
# if this is uninstallation as opposed to upgrade, delete the service

0 comments on commit 5083f2e

Please sign in to comment.