[Buildbot-devel] 2 repositories, 1 buildmaster

Cavanagh, Sean (Sean) scavanagh at avaya.com
Mon Aug 20 21:10:04 UTC 2007



Is your problem schedulers or builders?  Can you run the builds manually
from the buildbot web page?  If so, and your problem is getting them to
run automatically, when exactly do you want builds to be triggered?
Both builds whenever a dev submits anything?  One build when some files
churn the other build when other files churn?  Nightly?


Like Matthieu, I have multiple projects running on the same master
driving three different slaves, with no trouble.


Sean C.



From: buildbot-devel-bounces at lists.sourceforge.net
[mailto:buildbot-devel-bounces at lists.sourceforge.net] On Behalf Of
Matthieu Brucher
Sent: Monday, August 20, 2007 12:38 PM
To: buildbot-devel at lists.sourceforge.net
Subject: Re: [Buildbot-devel] 2 repositories, 1 buildmaster



I use buildbot on two separate projects, one with CVS the other one with
SVN with the same buildmaster, no problem.


2007/8/20, Benoit SIGOURE < tsuna at lrde.epita.fr
<mailto:tsuna at lrde.epita.fr> >:

On Aug 20, 2007, at 5:34 PM, Ged wrote:

> I have 2 separate repositories on my svn server hosting 2 different 
> projects.
> This server also hosts a buildmaster which is currently building
> one of
> these 2 project.
> I'd like to add the second project to the buildmaster but I'm
> having trouble
> configuring it to treat the 2 projects seperatley.
> Can someone outline what I need to do to get these 2 projects treated
> seperatley.
> Both project has it's own separate build slave. 
> Thanks,
> Ged.

As far as I know you must setup one buildmaster per project.
This question already came to the list (e.g.: http://thread.gmane.org/
gmane.comp.python.buildbot.devel/1498/focus=1502) and that's the kind
of problem I ran into when I did my 1st buildbot setup until I
realized that the only way to do it is to have separate buildmasters.

One of the thing that annoys me most is that I frequently fall in 
this scenario: I have a SVN repository where people develop libfoo.
I another SVN repository, some other people develop a program `bar'
that uses `libfoo'.  I another SVN repository, some other people
develop a friendly GUI around the raw CLI program `bar' (name it
`qux').  With BuildBot, you must setup 3 buildmasters.  Ideally, you
want that whenever a dev commits something in libfoo and the build
succeeds, then `bar' be rebuilt with the new libfoo.  Unfortunately, 
there is no way ATM to trigger a build in another buildmaster
(although I guess this should be fairly easy to do since the whole
code required is already there, in the commit hooks.  The only thing
needed is a buildstep that makes it easy to add this at the end of a 
build process).  So what I do ATM is that dependent projects (`bar'
and `qux') are rebuilt frequently with a Periodic scheduler (e.g.
every 5 hours).


Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop. 
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Buildbot-devel mailing list
Buildbot-devel at lists.sourceforge.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20070820/80d12024/attachment.html>

More information about the devel mailing list