On Fri, 12 Aug 2011 09:01:14 -0500 Zach Pfeffer <zach.pfef...@linaro.org> wrote:
> Oh, the other thing is to generate the pinned-manifest.xml before the > build is made so that the build comes from the pinned-manifest. > This'll save us a step. One reliable way to do this is tagging, like I argued the other time. We start build with tagging all components with (special) tag for this builds number. Then checkout exactly that tag (that will be a bit more complicated than usual with repo and its manifests), then do build, then can reproduce it 100% without recoursing to raw SHA1 revids. If one specific build is useful, we can re-tag it "normal" tags. Otherwise, those special build tags will be expire after some time t avoid pile-up. > > On 11 August 2011 22:26, Zach Pfeffer <zach.pfef...@linaro.org> wrote: > > Paul, > > > > I was wondering if we could make a small change to android-build. I > > just recently tested: > > > > https://android-build.linaro.org/builds/~linaro-android/leb-panda/#build=166 > > > > It works great and I'd like to move it to a first 11.08 release. Its > > based on toolchain: > > > > https://android-build.linaro.org/jenkins/job/linaro-android_toolchain-4.6-2011.07/8/artifact/build/out/android-toolchain-eabi-linaro-4.6-2011.07-0-8-2011-07-25_12-42-06-linux-x86.tar.bz2 > > > > I'd like to simply mark this build as "releasable" and have it save > > the toolchain and commit the pinned-manifest.xml to 11.08. > > > > Any thoughts? > > > > -Zach > > -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
