You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2013/11/25 06:16:46 UTC

[jira] (MRM-1782) SNAPSHOTS not getting purged

     [ https://jira.codehaus.org/browse/MRM-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MRM-1782.
-----------------------------

    Resolution: Fixed
      Assignee: Olivier Lamy
    
> SNAPSHOTS not getting purged
> ----------------------------
>
>                 Key: MRM-1782
>                 URL: https://jira.codehaus.org/browse/MRM-1782
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository interface, repository scanning
>    Affects Versions: 1.4-M4
>         Environment: Windows Server 2008, Tomcat 7, PostgreSQL 9.2, Jenkins
>            Reporter: Chris Harris
>            Assignee: Olivier Lamy
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: TheHordeOfSnapshots.png
>
>
> I've configured Jenkins to deploy snapshots to an internal snapshot repo that houses in-house artifacts upon successful builds.  Jenkins is doing its job and deploying successful builds to Archiva.  However, the artifacts keep accumulating!
> Repository scanning is set to:
> Enabled 	repository-purge 	Purge repository of old snapshots
> The snapshot repo's relevant settings are:
> Cron Expression: 0 0 * * * ?
> Days Older: 2
> Retention Count: 2
> Snapshots, Scanned, and Delete Released Snapshots are the only check boxes that are checked.
> I've included a screen shot of just one of the artifacts that I'm manually having to purge.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira