Not sure...what is Google/OHA using as their 'buildbot' setup?

Fred Grott
http://mobilebytes.wordpress.com


On Tue, Jul 7, 2009 at 1:59 AM, anantvijayk <[email protected]>wrote:

>
> Hi all,
>
> I've setup a buildbot for android. Android doesn't use "Git" commands
> directly, but instead uses a command called "repo" to checkout out the
> source. So i cannot use the git source step in the buildbot.
>
> My source checkout step is:
> f1.addStep(shell.ShellCommand, description= "Initialize the repo, sync
> and checkout the tag", command= "repo_init.sh", haltOnFailure=True)
>
> The repo_init.sh is the script which runs the commands:
> repo init -u git://android.git.kernel.org/platform/manifest.git
> repo sync
> repo forall -c git checkout TAGXYZ
>
> This is working quite fine, but there is an issue with the source
> stamp. It always shows the branch "HEAD" instead of the tag being
> checked out "TAGXYZ". Browsing through the buildbot source (buildbot/
> steps/source.py), found that the revision is being set in the source
> checkout step of each version control system. But since the "repo"
> command is not supported in the buildbot, how do i go ahead to set the
> revision?. Also the waterfall results page shows as
>
> Recent Builds:
> (Jul 07 00:30) rev=[??] success #14: build successful
> (Jul 06 00:30) rev=[??] failure #13: failed shell_4
> (Jul 05 00:30) rev=[??] failure #12: failed shell_4
> (Jul 04 00:30) rev=[??] failure #11: failed shell_4
> (Jul 03 00:30) rev=[??] failure #10: failed shell_4
>
> You can make out that the revision is being shown as question marks.
> I'm using a nightly scheduler.
>
>
> Any help???
>
>
> Thanks,
> Anantvijay
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Android Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/android-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to