Hello Bernhard,
On Mon, 14 May 2012 14:40:36 +0200 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
Hi,
On 14 May 2012 14:11, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
linaro-android_imx53-ics-gcc47-freescalelt-stable-open linaro-android_imx6-ics-gcc47-freescalelt-stable-open linaro-android_origen-ics-gcc47-samsunglt-stable-blob linaro-android_origen-ics-gcc47-samsunglt-tracking-blob linaro-android_panda-ics-gcc44-kwg-upstream-open linaro-android_panda-ics-gcc47-tilt-stable-blob linaro-android_panda-ics-gcc47-tilt-tracking-blob linaro-android_panda-master-gcc44-aosp-stable-blob linaro-android-restricted_vexpress-rtsm-isw-ics-gcc46-armlt-stable-open linaro-android-restricted_vexpress-rtsm-isw-ics-gcc47-armlt-stable-open linaro-android_snowball-ics-gcc46-igloo-stable-blob linaro-android_snowball-ics-gcc46-igloo-tracking-blob linaro-android_snowball-ics-gcc47-igloo-tracking-blob linaro-android_vexpress-ics-gcc47-armlt-tracking-open linaro-android_vexpress-rtsm-ics-gcc47-armlt-stable-open
For all of those, I think it would be great to have a "if anything changed" switch -- check out the manifest, compare the checksums to those of the latest build, and if they all match and the compiler hasn't changed, don't do the build.
Yes, that was raised couple of times, but so far we don't have machinery for that. Nor it's really that easy. For manifests which don't have tags/SHAs, it should check actual underlying repos. Then there's non-git repos, like toolchain builds you mention below. Then we want advanced trigger logic - "build daily if there were any changes" (to start unconditionally and check for updates as part of build already wastes 1 machine-hour). Then we should see how this fits/interacts with pre-merge test builds from Gerrit changes (which we kinda have but which grew unmaintained, I wonder if people remember about them). So, instead of trying partial quick hacks, we'd better think how to get full-feature, flexible and reliable system. Hopefully, something to discuss at Connect.
linaro-android_toolchain-4.5-bzr
The frequency of this can probably be reduced even more. I don't think we'll be making any more 4.5 based releases unless some really serious issue shows up.
linaro-android_toolchain-4.6-bzr
Given we've pretty much moved on to 4.7, I'd be ok with reducing the frequency of this one.
Sounds good on these 2, I'll go for that, unless concerns will be raised.
linaro-android_toolchain-4.7-bzr linaro-android_toolchain-trunk
Those should definitely stay (maybe also with a "only if anything changed" condition - but it's probably harder to do there given they pull in stuff from places not listed in the manifest.
ttyl bero