Disk usage plugin recalculates disk space usage based on a very, very lazy schedule. It is actually somewhat disk-intensive, so it is nice it doesn't run continuously.
Another way to save on disk space is to find the spot in job configuration where you configure the archived artifacts. Under it is a button titled Advanced. Click on that. More options will appear. Among them is an option to always delete old artifacts and only keep the latest. The job will still keep all the test results and other statistical history, only the artifacts are nuked (except the last). I use this option on one of my jobs that produces 1 GB of artifacts for every build. Of course it won't help if you need to keep more artifacts...... You can write a script that deletes the artifacts you do not need from the disk. Jenkins won't mind if they disappear. -- Sami Ed Young <e...@summitbid.com> kirjoitti 14.9.2012 kello 16.39: > the disk usage plugin is installed and is what I've been using to > determine which projects (mine) are the biggest disk hogs. > > One of my builds uses 18 GB of space. The next largest one is 1GB. The > reason it uses so much space is because I want keep 50 old builds > behind so that if I notice that test coverage has dropped, for > example, I can go back and see where that happened. I'm not sure of > any other way to track this kind of thing without keeping a large > number of builds. > > > On Fri, Sep 14, 2012 at 6:11 AM, Lars Nordin <lnor...@internap.com> wrote: >> -----Original Message----- >> From: Ed Young >> >> Scott, kicking off the build seems to have deleted the old builds, although >> I'm not seeing the diskspace usage go down the way I'm hoping. I have a lot >> of builds to reconfigure and kick off though so this make some time. >> -----Original Message----- >> >> You might want to install the disk usage plug-in and it help you find what >> jobs and builds are consuming the most disk space. >> https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin >> > > > > -- > - Ed
