Hello,
We keep having cases of out of disk space, latest we had is
https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1055546 .
The reason this happens so often is that Jenkins has a broken build
expiration process - it is applied to jobs which are actually built. If
a job is left unattended, its builds will stay forever. This is
long-standing known issue, and I manually deleted stale builds in this
case, while queuing need to write a script for that, which I'm going to
start with now.
To remind, we have following build retention policy:
1) Release builds stay forever
2) Official daily builds kept for 3 months
3) Personal builds kept for 1 month
With new expiration script to be developed, many builds will
be "suddenly" (but in full accordance with the policy above) gone. So,
I would like to ask all Android developers to look thru their builds to
check if you need anything old (and preserve it somewhere else then).
Zach, Fathi, Alexander, can you please do the same for old official
builds. For example,
https://android-build.linaro.org/jenkins/view/Official%20builds/job/linaro-android_beagle/
would be gone completely.
In addition to the above, the issue we may have that there're lot of
empty personal jobs piled up (with builds removed per the policy
above). They clutter view largely, for example, Bero has 10 such jobs,
Zach - 8, etc. Do you still need them? Otherwise, I'd propose to add
another clause to the policy and remove such empty jobs if not updated
within last 3 months. Let me know what you think.
What if we simplify this. We introduce a build variable that's a date or a value. Builds without such a variable disappear in a week, builds with it expire on the date show, builds marked FOREVER stick around.
Also, what about the underling disk space issues. Android build sizes will keep going up and the number of Android builds will keep going up. Can we just get a bigger disk?
Thanks,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog