-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: All
It would be nice to be able to configure each project to remove old builds if
the aggregate disk used for builds has reached X megabytes. This would provide
a cap on disk usage at the project level and enforced through the build process.
- is related to
-
JENKINS-18555 Send warn email to admin before disk space exceeds configured size per server and/or per job
-
- Resolved
-
[JENKINS-3433] Enhance 'Discard Old Builds' option to discard if build disk size is greater than X
Nicholas Fone
added a comment - On a large Jenkins master server, with 100's of jobs (or more!), disk usage can be a significant problem. Some jobs can easily generate 100MB of logs/history/reports, per build! On the other hand, some jobs might only generate 1MB.
In both cases, I think it would be very helpful be able to cap the total disk usage for each job in MB, rather than taking a guess at what values to use for the existing "days" and "builds" fields.
Also, +1 for Harry's implementation suggestion 
Nicholas Fone
added a comment - On a large Jenkins master server, with 100's of jobs (or more!), disk usage can be a significant problem. Some jobs can easily generate 100MB of logs/history/reports, per build! On the other hand, some jobs might only generate 1MB.
In both cases, I think it would be very helpful be able to cap the total disk usage for each job in MB, rather than taking a guess at what values to use for the existing "days" and "builds" fields.
Also, +1 for Harry's implementation suggestion 
Great idea! Best would be to have a field near the current attributes for how many days / builds to keep.