You can also look at the M2 Repository Cleanup Plugin [1] or another thread from the hudson list:
http://hudson.361315.n4.nabble.com/delete-local-maven-repository-td1102506.html [1] http://wiki.hudson-ci.org/display/HUDSON/M2+Repository+Cleanup+Plugin Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Sep 16, 2010 at 3:54 PM, Baptiste MATHUS <[email protected]> wrote: > Hi, > > This is almost more a hudson/ci problem than a maven one. > Well, in a CI server, you should just wipe out the local repository on a > regular basis. > > See > http://www.sonatype.com/people/2009/01/maven-continuous-integration-best-practices/ > and > http://batmat.net/blog/post/2009/10/09/[Hudson]-How-to-set-a-private-maven-repository-by-job-and-easily-be-able-to-delete-them > for > more hints about this subject. > > Cheers > > 2010/9/16 Lóránt Pintér <[email protected]> > >> Hi, >> >> I'm using Hudson to do nightly builds of the product we are working >> on. It deploys to Nexus, and it works beautifully. Every night we >> create like 800 MB of artifacts, and Nexus keeps the last 3 of each >> SNAPSHOT, so it uses a managable amount of disk space to do this. >> However, on the Hudson slaves, the SNAPSHOTs just accumulate and after >> some time occupy all the disk space available. >> >> Is there a way to deploy artifacts without using unique names in the >> local repo? Or maybe, is there a plugin I can use to remove the >> artifacts created previously by the build from the local repo? I found >> the purge-local-repository goal of m-dependency-p, but IIUC, it does >> the exact opposite to what I want to do. >> >> Thanks, >> Lóránt >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
