-
Bug
-
Resolution: Fixed
-
Critical
-
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.
Description |
Original:
Hudson 1.350 could delete your artifacts. After an upgrade the new fields introduced in Hudson 1.350: artifactDaysToKeep artifactNumToKeep ...are initialized to 0 for projects already using LogRotator. 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 |
New:
Hudson 1.350 could delete your artifacts. After an upgrade the new fields introduced in Hudson 1.350: artifactDaysToKeep artifactNumToKeep ...are initialized to 0 for projects already using LogRotator. 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 |
Description |
Original:
Hudson 1.350 could delete your artifacts. After an upgrade the new fields introduced in Hudson 1.350: artifactDaysToKeep artifactNumToKeep ...are initialized to 0 for projects already using LogRotator. 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 |
New:
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 |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JNJira [ 136029 ] | New: JNJira + In-Review [ 203810 ] |