On 4 July 2012 04:22, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 3 July 2012 05:59, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
Hello Zach,
On Mon, 2 Jul 2012 16:31:02 -0500 Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 26 June 2012 03:36, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
(This is forward of the original announcement of support of "build configs in git" feature, for reference.)
Begin forwarded message:
Date: Mon, 20 Feb 2012 18:11:42 +0200 From: Paul Sokolovsky Paul.Sokolovsky@linaro.org To: linaro-android linaro-android@lists.linaro.org, linaro-dev linaro-dev@lists.linaro.org, Zach Pfeffer zach.pfeffer@linaro.org, Danilo Šegan danilo.segan@linaro.org Subject: [ANN] Support for fetching build configs from git for Android Builds
Hello,
As the result of implementation of https://blueprints.launchpad.net/linaro-android-infrastructure/+spec/build-c... , android-build.linaro.org now can indirectly fetch build config stored in a git repository. To achieve that, bootstrap config (as specified in android-build.linaro.org) should contain reference to config's repo/branch/file (configuration variables are modeled on the similar MANIFEST_* ones), e.g.:
BUILD_CONFIG_REPO=git://git.linaro.org/people/pfalcon/android/linaro/build-configs.git BUILD_CONFIG_BRANCH=master BUILD_CONFIG_FILENAME=panda-ics-gcc46-tilt-tracking-blob.conf
Paul,
What changes do you think would be necessarily to use:
MANIFEST_REPO=git://android.git.linaro.org/platform/manifest.git MANIFEST_BRANCH=linaro_android_4.0.4 MANIFEST_FILENAME=staging-origen.xml
...but to use a config that came from a git in the manifest?
So you'd clone the build based on this info ^^^^^^
...but then you'd read the config that got checked out?
Well, if I understand correctly what you want, it's not supported - build config either comes completely from the interactive form in build frontend, or completely from git, you can't mix the both. That was kind of requirement for design of the git build config feature - to make sure that complete config comes from a well-known location, and tracked for changes in its entirety.
Sure, but assuming we want to change it so that the build gets kicked off from:
MANIFEST_REPO=git://android.git.linaro.org/platform/manifest.git MANIFEST_BRANCH=linaro_android_4.0.4 MANIFEST_FILENAME=tracking-panda.xml
but then:
TARGET_PRODUCT=pandaboard TARGET_SIMULATOR=false TOOLCHAIN_URL=http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-2012.06/5/... TOOLCHAIN_TRIPLET=arm-linux-androideabi REPO_SEED_URL=http://android-build.linaro.org/seed/uniseed.tar.gz LAVA_SUBMIT=1 LAVA_SUBMIT_FATAL=0 TARGET_NO_HARDWAREGFX=1 KERNEL_CONFIG=omap4plus_defconfig LAVA_ANDROID_BINARIES=False LAVA_TEST_PLAN="busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey" MONKEY_RUNNER_URL_1="git://android.git.linaro.org/test/linaro/android/system.git"
is all kept in a git, in the build. What would need to change?
Nothing from infrastructure side. We just need to update the build configurations and make sure the manifest are up-to-date in the git tree.
Again, we switched to use the git configs at some point then reverted because asac asked a better support. As a result, the following blueprint has been created: https://blueprints.launchpad.net/linaro-android-build-tools/+spec/android-bu...
http://android.git.linaro.org/gitweb?p=linaro/build-configs.git%3Ba=summary was created to store configs for the official builds in the Gerrit tree.
Sample job is available here: https://android-build.linaro.org/builds/~pfalcon/git-build-config/ (it uses personal repo as a test).
-- Best Regards, 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
-- Best Regards, 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
-- Best Regards, 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
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android