You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/04/02 07:57:58 UTC

[jira] Updated: (CONTINUUM-1693) Continuum fills our server disk with SNAPSHOTs.

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

Brett Porter updated CONTINUUM-1693:
------------------------------------

    Fix Version/s: 1.2

> Continuum fills our server disk with SNAPSHOTs.
> -----------------------------------------------
>
>                 Key: CONTINUUM-1693
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1693
>             Project: Continuum
>          Issue Type: Bug
>            Reporter: Geert Pante
>             Fix For: 1.2
>
>
> Our Deployment Repository Directory fills our server disk with SNAPSHOTs after running hourly builds for a couple of weeks.
> We have more or less a hundred applications configured in Continuum. A lot of them create assemblies with all their dependencies embedded, so each snapshot deployed eats a couple of megabytes. We also need hourly builds.
> We use 'maven clean deploy' to deploy these snapshots to a dedicated Archiva snapshot repository. In Archiva, these snapshots get purged after a week, only keeping the last 2 or 3 snapshot versions.
> However, continuum always installs to the local repository first, before uploading them to Archiva. This repository never gets purged. I was thinking to have Continuum use Archiva's repository directly as internal repository, but I don't know if that's safe or not. Archiva won't know these changes before it scans the repository again.
> I was also looking at maven-dependency-plugin:purge-local-repository, but that's not exactly what we want. We just want to purge old snapshot versions when new snapshot versions are installed. Maybe that could be a general Maven feature, but it is especially important for Continuum.

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