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
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
Hi Ed,
Try the Workspace Cleanup Plugin and configure it to wipe out your
workspace after the build is done.
cheers,
Chris
On 14/09/2012 14:39, Ed Young wrote:
the disk usage plugin is installed and is what I've been using to
determine which projects (mine) are the biggest disk hogs.
One
I need to clear out some drive space on our build machine by deleting
old builds, but manually selecting each one and deleting it is too
painful.
If I change Max # of builds to keep from 100 to 10, will Jenkins
automatically delete the 90 that I no longer want, or do I need to
delete them by
Ed,
Based on my experience, it will purge old builds (by date or quantity) only
when a new build of that type completes. In your case, once you run one,
it'll should automatically delete the 91 extra builds which are no longer
within the retention policies for that build type. Note that it will
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.
What do you mean by multiconfiguration builds?
On Thu, Sep 13, 2012 at
