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

Total Data loss because of jenkins version 1.535 extracts jenkins.war to directory "jenkins" since older versions extract to directory "war"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • core
    • None
    • debian lenny
      Jenkins 1.535

      We use following directory structure:

      .

      – jenkins
        – jenkins
        – jenkins.war
        – jenkins.war.bak
        – jenkins.war.tmp

      where ./jenkins was the path where jenkins was started by
      "java -jar jenkins.war .....".

      and jenkins/jenkins was our jenkins home directory (JENKINS_HOME).

      Until 1.534 the war archive was extracted to "./jenkins/jenkins/war" (=$JENKINS_HOME/war).

      Version 1.535 extracts to ./jenkins/jenkins which causes a removal of our whole jenkins home directory (thanks god we have a backup) replaced by the war archive content.

      Is there possibility to protect jenkins home directory against being the war extraction directory ?

      Our environment may be a little strange and we'll change it, but it was terrible, when a working environment was destroyed just by updating to a new version.

      I renamed the jenkins home directory ./jenkins/jenkins to ./jenkins/something and use it as JENKINS_HOME, and now the war archive was extracted again to $JENKINS_HOME/war as it was in earlier versions.

      Strange !

            Unassigned Unassigned
            wo_hauser Wolfgang Hauser
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: