continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geert Pante (JIRA)" <>
Subject [jira] Created: (CONTINUUM-1693) Deployment Repository Directory fills our server disk with SNAPSHOTs.
Date Thu, 13 Mar 2008 13:22:28 GMT
Deployment Repository Directory fills our server disk with SNAPSHOTs.

                 Key: CONTINUUM-1693
             Project: Continuum
          Issue Type: Bug
            Reporter: Geert Pante

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

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:
For more information on JIRA, see:


View raw message