You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2009/09/10 01:14:31 UTC

[jira] Closed: (CONTINUUM-1809) Purge old Build-Results

     [ http://jira.codehaus.org/browse/CONTINUUM-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak closed CONTINUUM-1809.
----------------------------------

      Assignee: Wendy Smoak
    Resolution: Duplicate

Closing as a duplicate of CONTINUUM-1696 only as I can't find the original issue for adding the build output purge.

You can already configure it to purge the build output, however that only deletes the text files, not the database records.

> Purge old Build-Results
> -----------------------
>
>                 Key: CONTINUUM-1809
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1809
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Database
>    Affects Versions: 1.1
>            Reporter: Marc Lustig
>            Assignee: Wendy Smoak
>
> If you do e. g. an hourly build, then the list of build-results will easily blow up after a couple of days, and so the database.
> There should be an option to configure the limitation of  the history of build-results, on either of the levels:
> - project-level
> - group-level
> - global level
> Old Build-Results should be purged automatically, i. e. without user-interaction.

-- 
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