On 26 September 2012 04:49, Paul Sokolovsky <paul.sokolovsky@linaro.org> wrote:
> 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).

Can we have a "keep this indefinitely" checkbox on builds?
I think that's primarily useful to keep around the last build when
support for a platform is dropped (Beagle, iMX53, iMX6, ...), but also
to keep a specific build around for debugging (e.g. last build showing
a bug that stopped appearing, but where we know it's not fixed -- e.g.
hidden due to different timing)

This is a good idea Bero, Paul/Danilo do you think this is a reasonable improvement you could make in 12.10? You could also then set the retention policy for anything not kept to 1 week. Thoughts?

> 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,

I've killed most of them. Keeping imx6-test for now just in case we
ever want to revive support for it.

ttyl
bero