Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12231

RPM upgrade does not honor JENKINS_USER, and always resets files ownership to "jenkins"

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Linux, CentOS and Fedora. Using RPM installation and upgrade

      I have a Jenkins installation for which I changed the "JENKINS_USER" and "JENKINS_HOME" (in /etc/sysconfig/jenkins) from the defaults.
      When I do an upgrade via yum/RPM, it sets the ownership of /var/log/jenkins back to default user "jenkins" (instead of honoring my JENKINS_USER configuration).

      This prevents Jenkins from starting after an upgrade. And since it cannot write to the log file, it may not be easy to figure out what went wrong.

          [JENKINS-12231] RPM upgrade does not honor JENKINS_USER, and always resets files ownership to "jenkins"

            Unassigned Unassigned
            fernando Fernando Dobladez
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: