You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "shadow_x99 (JIRA)" <ji...@codehaus.org> on 2009/02/27 15:16:20 UTC
[jira] Commented: (CONTINUUM-1696) Scheduled purge of old build
results
[ http://jira.codehaus.org/browse/CONTINUUM-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167312#action_167312 ]
shadow_x99 commented on CONTINUUM-1696:
---------------------------------------
Any news on that issue? This is turning out to be a major pain... When the database gets too poluted, you cannot even try to delete and/or move projects around, it just times out leaving the database in a stale state (i.e. Garbage left in the database).
> Scheduled purge of old build results
> ------------------------------------
>
> Key: CONTINUUM-1696
> URL: http://jira.codehaus.org/browse/CONTINUUM-1696
> Project: Continuum
> Issue Type: New Feature
> Components: Data Management
> Affects Versions: 1.1
> Reporter: Wendy Smoak
> Assignee: Olivier Lamy
> Fix For: 1.x
>
>
> Continuum should be configurable to automatically purge old build results.
> Similar to Archiva's snapshot purge, which allows you purge by date and/or keep the last X snapshots.
--
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