[
http://jira.codehaus.org/browse/MRM-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258734#action_258734
]
Brett Porter commented on MRM-1458:
-----------------------------------
This should be quite straightforward to do as a modification of the existing
purge tasks with appropriate configuration added. I can see the value in this,
though you need to be very careful about using it if you expect to have to
reproduce any historical builds, or if some artifacts are still in active use.
I would separate the repository that needs this rule from others.
If you'd like to submit a patch we'll certainly consider it.
Alternatively, you might like to take the existing consumers and add as a new
consumer within your own instance using Archiva's extensibility in this area.
> Repository purge options for released artifacts to improve usability of
> Search and Browse functions
> ---------------------------------------------------------------------------------------------------
>
> Key: MRM-1458
> URL: http://jira.codehaus.org/browse/MRM-1458
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.3.3
> Environment: Red Hat Enterprise Linux ES release 4
> Reporter: Markus Spann
>
> We work in a sort of agile way with (very) frequent releases. Our release
> repository currently has a file count of ~80,000 (total of jar, javadoc, and
> source artifacts).
> Most of these releases are actually obsolete and have long been superseded by
> more recent releases.
> To my knowledge there is not currently a way in Archiva to purge released
> artifacts (if not one by one or by manipulating the database/file system).
> The repository management screens in Archiva offer a (boolean) option to
> "Delete Released Snapshots". It would be very useful to have a repository
> purge options that applies to obsolete releases such as: "Keep only X most
> recent releases".
> Please note that despite large repository sizes we are encountering no
> noticeable performance issues (on an oldish x86 Red Hat Linux box). The
> feature will greatly improve usability of the Archiva Search and Browse
> functions.
--
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
