Is it possible to "prune" older builds?

[jimklimov]

What feature do you want to see added?

For the trunk of project development we would like to keep as much history as possible, so we can go back and compare how its code/coverage/build-duration/etc. quality fared over time, and notably when we might have first seen some "heizenbugs" (race conditions etc. that only happen once in a hundred builds and are swept under the rug until they are suddenly real bugs with a storied history).

Keeping truly everything over years of project development is not really feasible, so we would like SOME of the older builds deemed un-interesting pruned away -- e.g. keep one every month if they are older than a year, prefer to keep at least one green point in that month and those that did fail but only if they ran longer than X minutes and/or passed a milestone and/or have certain entries in log (like the SUT did get provisioned and initialized and tests actually ran and failed).

Is something like that possible with this plugin, either now or after reasonable tinkering? :)

Upstream changes

No response

Are you interested in contributing this feature?

50/50 - got some experience with both storage management and Jenkins plugins, but too overstretched on existing commitments.

[damianszczepanik]

This is quite complex to be supported by this plugin. I think you need to write your own custom implementation to meet above rules