continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Knecht (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-1693) Continuum fills our server disk with SNAPSHOTs.
Date Tue, 29 Apr 2008 13:21:46 GMT

    [ http://jira.codehaus.org/browse/CONTINUUM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132969#action_132969
] 

Felix Knecht commented on CONTINUUM-1693:
-----------------------------------------

Not sure, but looks like your using maven2.

You can deploy the snapshot file with name 'SNAPSHOT' instead of deploying the snapshot named
with timestamp. Thus an already existing snapshot file gets overwritten when deploying the
next snapshot.

See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html and search for
uniqueVersion.
Maybe it helps.

> 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

        

Mime
View raw message