[Buildbot-devel] 2 repositories, 1 buildmaster

Tue Aug 21 09:47:34 UTC 2007

Sean,

I assume it's a problem with my schedulers, I have no problems running the
builds seperatley from the web page.

What I need to do is have each individual build triggered when a commit is
made to it's repository.
Each project should be treated individually, as though running on 2
different buildmasters.

I have 2 seperate hook scripts in each repository to notify the buildmaster
with the required info.

At the moment, when a commit is made to either repository, both builds are
triggered.
I've tried altering the 'branch' parameter in the scheduler, but this
stopped both builds from triggering.

I'm trying to acomplish what you and Matthieu appear to have done.

Ged.

  _____  

From: buildbot-devel-bounces at lists.sourceforge.net
[mailto:buildbot-devel-bounces at lists.sourceforge.net] On Behalf Of Cavanagh,
Sean (Sean)
Sent: 20 August 2007 22:10
To: Matthieu Brucher; buildbot-devel at lists.sourceforge.net
Subject: Re: [Buildbot-devel] 2 repositories, 1 buildmaster

Ged,

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

Hi,

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

Matthieu

2007/8/20, Benoit SIGOURE <  <mailto:tsuna at lrde.epita.fr>
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).

Cheers,

--
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
https://lists.sourceforge.net/lists/listinfo/buildbot-devel
<https://lists.sourceforge.net/lists/listinfo/buildbot-devel> 

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. 

Amteus Secure Communications Ltd
57 Cardigan Lane,
Leeds, 
LS4 2LE
t: +44 (0) 870 8368770
f: +44 (0) 870 8368701

Registered in England No 4760795

http://www.amteus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20070821/7786bb34/attachment.html>