Comment 4 for bug 1055546

The plan was to develop a standalone Python script to parse Jenkins job/build XML configs and apply expiration settings in them. Well, I did another pass on trying to find what other people think about the behavior of Jenkins as described above. I found http://jenkins.361315.n4.nabble.com/Is-there-a-way-to-make-quot-discard-old-builds-quot-happen-right-now-td3879634.html , which suggests a Groovy script for builtin Jenkins interpreter.

It indeed did the tricks, so the good news is that we know have 150Gb free on android-build, with much less effort than developing a standalone script. The bad news is that this is interactive feature, so has to be run manually. And there's big temptation to leave it as is, because lot of disk space was already recovered. I'm not going to give so easy though, and will investigate how hard (and insecure) will be to cron'ize that Groovy script.