Using git for storing configs of all -tests builds

Zygmunt Krynicki zygmunt.krynicki at linaro.org
Tue Aug 7 08:31:34 UTC 2012


W dniu 07.08.2012 10:30, Zygmunt Krynicki pisze:

CCing the mailing list.

> Hello
>
> In accordance with blueprint: eng-and-test-builds [1]
>
> To implement the final work item of my blueprint I'd have to manually
> create (and later keep in sync) of the following configurations.
>
> *
> https://android-build.linaro.org/builds/~linaro-android/vexpress-ics-gcc47-armlt-tracking-open/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/vexpress-rtsm-ics-gcc47-armlt-stable-open/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/origen-ics-gcc47-samsunglt-stable-blob/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc46-igloo-stable-blob/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc47-igloo-tracking-blob/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc44-kwg-upstream-open/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-omapzoom-stable-blob/
>
>
> *
> https://android-build.linaro.org/builds/~linaro-android/vexpress-jb-gcc47-armlt-tracking-open/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-samsunglt-stable-blob/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/snowball-jb-gcc47-igloo-stable-blob/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/panda-jb-gcc47-tilt-tracking-blob/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/panda-jb-gcc47-tilt-stable-blob/
>
> *
> https://android-build.linaro.org/builds/~linaro-android/galaxynexus-jb-gcc47-aosp-blob/
>
>
> This screams as insane in my head so I went looking and recalled that
> Infrastructure has implemented feature where we can keep the configs in
> git. That would dramatically simplify everything.
>
> So, with that in context I'd like to propose three options and I'd like
> to ask you to pick the one you'd like to see implemented now:
>
> 1) Ignore git configs, duplicate everything manually and later check if
> it changes once a week to update -tests builds.
>
> 2) Create -tests builds manually but pull the configs from git. We still
> need to keep them in sync manually (with the base configs) but at least
> updates are easy to manage (one commit instead of a messy edit-and-save
> on dozen pages)
>
> 3) Move all existing configs to git, have a flag day, move all builds to
> git. Derive -tests builds from -eng builds. This is by far the most
> 'lazy' solution (as in I'm too lazy to do all the manual work all the
> time in the future) but has the most risk.
>
> pfefferz, asac: please decide and let me know
>
> pfalcon: for something like -tests builds it would be perfect if we had
> a include feature, where one config can include some other (presumably
> 'base') config and just override something. It's not a strict
> requirement for implementing -tests builds sensibly but it would be an
> advantage, is that supported by any chance? (are those shell files I
> could just source with something like '. base.conf')
>
> Best regards
> ZK
>
> [1]
> https://blueprints.launchpad.net/linaro-android/+spec/eng-and-test-builds
>


-- 
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/




More information about the linaro-android mailing list