[Buildbot-devel] 'try' for multiple repos

Marc-Antoine Ruel maruel at chromium.org
Wed Apr 7 21:08:32 UTC 2010

We use a 3-steps update mechanism for gclient-based try:

1) Sync to specified master revision/hash
2) Apply the patch
3) Sync again in case a DEPS file has been modified, the equivalent of
repo's manifest.

It works fine.

Le 7 avril 2010 14:00, Uma Sridharan <uma285 at gmail.com> a écrit :

> It still seems to be alright to build a repo SCM extension and use it
> instead of git. But it looks harder to extend 'try' to gather patches from
> these multiple repositories.
> 2010/4/7 Benoît Allard <benoit at aeteurope.nl>
>  Uma Sridharan wrote:
>>> Hi all,
>>>  I am trying to setup Buildbot for android builds that deals with
>>> multiple repositories. Could anyone tell me if there exists a way by which I
>>> can use 'try' command to capture changes in multiple repositories? Right now
>>> it works fine if I made changes to a single repository and called the 'try'
>>> command.
>> The quick answer is that buildbot has no support yet for multiple
>> repositories inside one project. There are way to make it works, but you
>> already found a corner case, and some more are to be found I guess.
>> This is for sure a planned improvement.
>> Regards,
>> Benoit
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20100407/e4bbe867/attachment.html>

More information about the devel mailing list