Upgrading to jenkins-2.537-1.noarch on OpenSUSE breaks configuration

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • Component/s: core
    • Environment:
      Jenkins 2.537
      OpenSUSE Leap 15.6

      I Just upgraded Jenkins to version 2.537 through zypper on OpenSUSE Leap 15.6. This changed my configuration files, prompting me to re-configure the system. I restored the saved configuration files, but having this happen in an undocumented manner does not look right.

       

      Abrufen: jenkins-2.537-1.noarch (jenkins)                   (1/1),  91,6 MiB    
Abrufen: jenkins-2.537-1.noarch.rpm ..........................................................................................................................................<74%>=================================================[- (30,7 MAbrufen: jenkins-2.537-1.noarch.rpm .....................................................................................................................................................................................[fertig (22,0 MiB/s)]
Überprüfung auf Dateikonflikte läuft: ................................................................................................................................................................................................[fertig]
warning: /etc/zypp/repos.d/jenkins.repo saved as /etc/zypp/repos.d/jenkins.repo.rpmsave
warning: /etc/sysconfig/jenkins saved as /etc/sysconfig/jenkins.rpmsave
(1/1) Installieren: jenkins-2.537-1.noarch ...........................................................................................................................................................................................[fertig]

      New repo file:

      [jenkins]
name=Jenkins
enabled=1
autorefresh=0
baseurl=https://pkg.jenkins.io/opensuse
type=rpm-md
keeppackages=0

      Old repo file:

      [jenkins]
enabled=1
autorefresh=1
baseurl=https://pkg.jenkins.io/opensuse/
type=rpm-md

      This means the automatic refreshing has been disabled.

      Moving the sysconfig file would change the data directory as well, leading to the aforementioned issue which prompted me for a new installation.

       

       

            Assignee:
            Unassigned
            Reporter:
            Stefan
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: