[Buildbot-devel] Multiple projects

[Benoît Allard]

On 2/23/2012 3:43 PM, Klaim - Joël Lamotte wrote:
> I didn't reply to the list so I'm resending it.
>
> 2012/2/23 Klaim - Joël Lamotte <mjklaim at gmail.com
> <mailto:mjklaim at gmail.com>>
>
>
>
>     2012/2/23 Tom Prince <tom.prince at ualberta.net
>     <mailto:tom.prince at ualberta.net>>
>
>         Yes. The situation that buildbot doesn't currently handle (but
>         which is
>         actively being worked on), is the case when you need to checkout
>         multiple repositories together, for a single build.
>
>
>     Thanks Tom, it's perfect for me.
>
>     Although, in I think several months in the future, I might need to
>     separate one of my projects in serveral repositories. I'm using
>     Mercurial, to be precise.
>     So, if I make that separation, but I have one special repository
>     that use subrepos, meaning import other repositories at specific
>     versions together; if I bind only this "all_together" repo to
>     buildbot master as one project, my understanding is that it will
>     update all the sources even from repos anyway and buildbot will only
>     "see" one repository.
>     So if I'm correct, even the current buildbot should be able to
>     handle this case.
>
>     Am I correct again?
>

You're correct, by using subrepo, Buildbot wil only see one repository. 
the trick however, will be to trigger your buildbot if you made 
modification to one of the subrepo ... In this case, you will need a 
special handling to instruct your buildbot to fetch the top repository 
and not the one the modifications happened on. And when you'll succeed 
to fetch the top repository, you'll need to instruct him to fetch for 
this other repository the modified revision, and not the one he knows about.

... Or you will only trigger your buildbot upon modifications of the 
root repository.

Regards,
Benoît.