|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
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![]()