On Wed, Sep 26, 2012 at 1:49 PM, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
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:
- Release builds stay forever
- Official daily builds kept for 3 months
- 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).
It's not clear what the new expiration script will do. Can you summarize what will change?
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-a... 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.
Also discussed during Leads meeting:
1. make a "release build" tab; keep release builds forever confirmed 2. make a "regression build" tab where all the variation builds we don't officially release go; those will get a 1 month retention 3. later: rename the Official build tab to something better.
With that a bunch of currently official builds will get a reduced retention which would give us more room to breeze.
Thanks, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog