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

New LogRotator fields can trigger unwanted deletion of artifacts.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • None

      Hudson 1.350 could delete your artifacts.

      After an upgrade the new fields introduced in Hudson 1.350:

      project.logRotator.artifactDaysToKeep
      project.logRotator.artifactNumToKeep

      ...are initialized to 0 for projects already using LogRotator.

      (In UI: "Days to keep artifacts" / "Max # of builds to keep with artifacts")

      This means that all your old artifacts will be deleted if you do not reconfigure the projects and reset the new fields to correct values.

      Issue was introduced with patch:
      http://fisheye.jenkins-ci.org/changelog/Hudson/?cs=28293

      Discussion at:
      http://n4.nabble.com/Warning-about-Hudson-1-350-Could-delete-your-artifacts-td1593483.html

          [JENKINS-5937] New LogRotator fields can trigger unwanted deletion of artifacts.

          Kohsuke Kawaguchi added a comment -

          Fixed in rev.28625 (and a few follow up commits to that file).

          1.351 is being released as we speak with this fix.

          Kohsuke Kawaguchi added a comment - Fixed in rev.28625 (and a few follow up commits to that file). 1.351 is being released as we speak with this fix.

            Unassigned Unassigned
            Glundh Glundh
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: