You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Marc Lustig (JIRA)" <ji...@codehaus.org> on 2008/06/23 15:19:27 UTC
[jira] Commented: (MRM-846) "Repository Purge By Retention Count"
option not working
[ http://jira.codehaus.org/browse/MRM-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139311#action_139311 ]
Marc Lustig commented on MRM-846:
---------------------------------
btw, the consumer "repository-purge" is enabled, of course.
> "Repository Purge By Retention Count" option not working
> --------------------------------------------------------
>
> Key: MRM-846
> URL: http://jira.codehaus.org/browse/MRM-846
> Project: Archiva
> Issue Type: Bug
> Components: repository interface
> Affects Versions: 1.0.2
> Environment: Linux, JBoss, Continuum SNAPHOT (19/06/2008)
> Reporter: Marc Lustig
> Priority: Critical
>
> from http://archiva.apache.org/docs/1.0.2/adminguide/repositories.html:
> "If the repository purge by retention count field is set to 2, then only the artifacts artifact-x-20070113.034619-3.jar, artifact-x-20070113.034619-3.pom, artifact-x-20070203.028902-4.jar and artifact-x-20070203.028902-4.pom will be retained in the repository. The oldest snapshots will be deleted maintaining only a number of snapshots equivalent to the set retention count."
> This is not working here. The value for "Repository Purge By Retention Count" is ignored, at least for the Snapshot-managed-repo.
> Old artifacts are not deleted.
> We are building new snaphot's on hourly basis using Continuum.
> The disk-space is heavily increasing and nothing is purged.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira