[
https://issues.jenkins-ci.org/browse/JENKINS-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160304#comment-160304
]
Emil Sit commented on JENKINS-8392:
-----------------------------------
This issue reveals that there are two ways to remove builds inside Jenkins...
one is handled by the LogRotator class (which has settings like, keep builds
for a certain number of days, and keep artifacts for a certain number of days)
and the other is handled by the ArtifactArchiver class (which has this
latestOnly option that the OP has described in the description). The problem
could be considered that these two classes don't respect each other's logic and
Jenkins does not bring a conflict between the two settings (e.g.,
ArtifactArchiver is configured to throw things away, but LogRotator is
configured to keep things around for some period of time) to light for the user.
> Keep release build artifacts forever
> ------------------------------------
>
> Key: JENKINS-8392
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8392
> Project: Jenkins
> Issue Type: Improvement
> Components: release
> Affects Versions: current
> Reporter: fredg02
> Assignee: Peter Hayes
> Priority: Minor
>
> I just recently learned that "keeping a build forever" does not necessarily
> mean that it's artifacts are also saved forever.
> Right now I try to keep the number of saved artifacts to a minimum by
> selecting the "Discard all but the last successful/stable artifact to save
> disk space"-option, but this also deletes the artifacts of old release builds!
> It would be nice to have an option in the release build section that allows
> me to keep the artifacts for all release builds, no matter if the "Discard
> all but the last successful/stable artifact to save disk space"-option or the
> "Discard Old Builds"-option are selected or not.
> I have not found an easy workaround for this so far, that's why I created
> this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
