|
||||||||
|
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/d/optout.
Why not keep a single file per job listing disk usage for every build? (Possibly in properties format, if the content is sufficiently simple.) This would be a lot faster to load than hundreds of little XML files. Of course you would need to update it when a new build is created; unnecessary to do so when an old build is deleted, since you can just ignore entries for builds whose directories (Run.id) do not still exist.