> CouchDB has 300+ builds from July taking up 100-150MB each. I’m not > sure why these wouldn’t have been removed by the ‘days to keep old > items’ parameter, so we’ll need to look into that on the infra side > as well. If the addition of the ‘max # of old items’ parameter > doesn’t purge them after the next build, we can remove them > manually. If infra does have to go and do some manual pruning, these > are the types of things we’ll be looking for and removing. > > Just looking at the build history in the Jenkins UI for the CouchDB > ‘master’ branch, it’s clear that the ‘days to keep old items’ > setting doesn’t seem to be working at all, since you have saved > builds back to November. Something else we’ll need to look into. I > doubt you were even aware of the July artifacts (I’m not sure how > you’d be able to see those.)
That's odd, thanks for letting us know, Chris. If INFRA can fix the problem as to why the very old builds are still hanging about, hopefully you won't have to resort to such drastic measures as deleting everything older than a certain date. We were going to look into using the Promoted Builds plugin in the new year to save builds for RCs and released versions; if you code something to delete old builds, would it be possible for it to not just blanket delete things older than a certain amount? The idea, again, is repeatable builds towards release-able assets with saved logs for traceability and audit trail. If we can't use Jenkins for this, we'll have to invent our own system (at considerable labour/expsnse.) -Joan
