You can (in a one of the latest Jenkins) set the private repo to be per executor. You can then schedule a job to run on that executor periodically to rm –fr privaterepo.
This has drawbacks as an “mvn install” from one job is visible to all other jobs on the same executor, whereas you really only want the results of mvn deploy to be visible. The other alternative is to take a look at https://wiki.jenkins-ci.org/display/JENKINS/Maven+Repo+Cleaner+Plugin Note I have done neither, so YMMV. /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jorg Heymans Sent: 16 May 2012 09:12 To: jenkinsci-users@googlegroups.com Subject: keeping m2 repository disk space under control Hi, For a large (100+ m2 jobs) Jenkins instance, what are my options to control the diskspace taken up by the jobs' private m2 repos ? Since maven does not handle access to its own local repo transactionally (vote here http://jira.codehaus.org/browse/MNG-2802) we need to set a private local repo per job. Has anyone been able to tackle this in some way or another ? Thanks ! Jorg ________________________________ ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **************************************************************************************
