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

Reply via email to