Hello Bernhard,
On Wed, 26 Sep 2012 15:19:39 -0700 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
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?
There's such feature in Jenkins. It is not exposed in Build Frontend though. For example, when logged in with job edit permission, go to https://android-build.linaro.org/jenkins/job/berolinux_nexus7-jb-gcc47-aosp-... , at the top right corner of page, there's "Keep this build forever" button. Then, there's "add description" link-button, which allows to add notes to a build.
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)
Definitely, that's useful. When I was full-time on Android build infra, I used those features myself to annotate type of breakage a build had, or mark last build before an Android version upgrade and first after, etc. (cannot give examples, because we had several rounds of build renames since, so I cannot quickly find an instance).
Well, I never had a feedback that someone finds my annotations useful, or even notices them. (And there's of course good reason for that - we wanted people to use frontend, so people used it, while annotations are in Jenkins).
Bernard, as you have enough access to Jenkins to use those features, I'd welcome you to try them, and let's see how useful and used they actually will be.
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.
Thanks!
ttyl bero