gerrit-bot does not pick the right manifest for build

[vishal]

http://review.android.git.linaro.org/#change,827 was relevant to tracking-panda /staging-panda builds ,where as the gerrit-bot tried to download the default manifest for build.

Moving ahead we would end up with a single manifest(ideally) but presently there is no mechanism for gerrit-bot to decide on which manifest should be chosen to test a particular review.

[Frans Gifford (fgiff)]

At the moment we use some heuristics to try to avoid this sort of situation, in particular, we avoid known problems such as device/*, toolchain/* and so on.

There's no guarantee that the manifest we use for testing contains the project the change is in. There's also no reliable way to work out what manifest we should be using, or if we should be adding the project to a .repo/local_manifest.xml.

I'll create a BP to investigate better ways to deal with projects that only appear in a subset of release manifests.

[Yongqin Liu (liuyq0307)]

why the change http://review.android.git.linaro.org/#change,1034 is relevant to this bug,
and the change is on linaro_android_4.0.1 branch, and the gerrit was to check branch linaro_android_2.3.5

+ repo init -u git://android.git.linaro.org/platform/manifest.git -b linaro_android_2.3.5 -m default.xml

but why it also tried to apply the changes?

+ /mnt/jenkins/workspace/gerrit-bot_pandaboard/build-tools/build-scripts/apply-gerrit-change device/ti/panda 1034 2

[Frans Gifford (fgiff)]

Currently, gerrit-bot builds all changes against this build job: https://android-build.linaro.org/builds/~gerrit-bot/pandaboard/ which is currently a GB job, so will inevitably have issues when people submit ICS changes.

I'll submit a separate bug to update the job to be an ICS build since that's what most bug fixes will target.

[Alan Bennett (akbennett)]

Due to the age of this issue, we are acknowledging that this issue will likely not be fixed. If this issue is still important, please add details and re open the issue.