Nah - no need to be that drastic - maven2 project type to the rescue! Just set a different retention for artifacts vs builds.
Discard Old Builds Days to keep builds if not empty, build records are only kept up to this number of days Max # of builds to keep if not empty, only up to this number of build records are kept Days to keep artifacts if not empty, artifacts from builds older than this number of days will be deleted, but the logs, history, reports, etc for the build will be kept Max # of builds to keep with artifacts if not empty, only up to this number of builds have their artifacts retained From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly Sent: 21 September 2012 15:56 To: jenkinsci-users@googlegroups.com Subject: Re: Taking a lot of disk space Aha! Maven 2 project type strikes again! It auto-archives every build artifact... I think you can disable this setting... but you risk reduced functionality in some use cases On 21 September 2012 15:49, Miguel Almeida <migueldealme...@gmail.com<mailto:migueldealme...@gmail.com>> wrote: Hi Marek, On Fri, Sep 21, 2012 at 3:36 PM, Marek Gimza <marekgi...@gmail.com<mailto:marekgi...@gmail.com>> wrote: Miguel, Is the workspace directory under the /usr/share/tomcat6/.jenkins/jobs/<job-name> directories? It is. But the workspace directly below <job-name> is only 100 MB large, so it's hardly the problem. Running some "du" commands, I see most space is being occupied by the builds directories under each module: /usr/share/tomcat6/.jenkins/jobs/<job-name>/moduleA/builds. One of them has...15GB of data! This could be the reason for the disk usage. The workspace is the directory to which jenkins will sync and perform your build-steps. You could take advantage of the "customWorkspace" field in the job configuration or the "Remote FS root" field in the Node's configuration to specify a different directory to store the workspace. We use these fields to specify our workspace for each job to be different than the job's meta-data, such as log-files, which is still under the ${JENKINS_HOME}/jobs/<job-name> directories. Kind Regards, Marek On Fri, Sep 21, 2012 at 10:26 AM, Miguel Almeida <migueldealme...@gmail.com<mailto:migueldealme...@gmail.com>> wrote: Dear all, I have been using Jenkins for some months now and I am interested in the issue of disk usage. While trying to understand why the 50GB on the server were becoming short, I decided to investigate the size of each job directory under /usr/share/tomcat6/.jenkins/jobs/. To my surprise, this was larger than expected. One maven job with 5 modules and about 700 runs is currently taking 16 GB of disk space! I realize I can "discard old builds" of a job, but then I'll lose interesting metrics like code coverage trends or test result trends. My questions are: 1) Is this a normal usage - 23-ish MB per job run? 2) If so, are there other options that allow me to keep a relatively interesting history but without taking so much disk space? 3) Is this a usual concern, or do you just splash new TB disks whenever you run out of space? I mean, I've been using Jenkins for 10 months and have around 20 projects now, surely this is not intensive usage. I appreciate the feedback, Miguel Almeida ________________________________ ************************************************************************************** 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 **************************************************************************************
