Build output increasing repository size uncontrollably
Accepted answer
First make sure that the BuildResultPrunerTask is running in the server administration page. Then make sure that the task is running at an appropriate interval, by default its 15 minutes. But most importantly the prune task is capped at 50 items per run. So if more builds are generated than can be handled with the cap, then the database size will keep increasing.
Running multiple builds often every day is causing the database to increase in size every day even though the pruning option is turned on for the build definitions. Why are the builds increasing every day if they are getting pruned?