[Buildbot-devel] 2 repositories, 1 buildmaster

[Ged]

Hi Roch,
 
Thanks for this, it works great!
I updated my buildserver with your patches today, everything now works as I
wanted, the 2 projects are completely independent.
 
Cheers,
Ged.

  _____  

From: buildbot-devel-bounces at lists.sourceforge.net
[mailto:buildbot-devel-bounces at lists.sourceforge.net] On Behalf Of Roch
Gadsdon
Sent: 21 August 2007 11:14
To: Matthieu Brucher; BuildBot Devel
Subject: Re: [Buildbot-devel] 2 repositories, 1 buildmaster


Hi Ged / all, 

We came across this too when we setup our BuildBot / Subversion environment.

Our solution was to modify the scheduler and change handling code and
Subversion change sending hook to include a "repository" parameter as well
as the branch.

This is working for us and we submitted patch 1685062 on SourceForge with
the changes. See http://sourceforge.net/tracker/index.php?func=detail
<http://sourceforge.net/tracker/index.php?func=detail&aid=1685062&group_id=7
3177&atid=537003> &aid=1685062&group_id=73177&atid=537003

A word of warning. This isn't a patch that has (yet?) been discussed /
adopted / reviewed by the BuildBot community so it may well have drawbacks;
but, as I say, it works for us and it's there if you want to try it.

Cheers,

-- Roch Gadsdon

On 21 Aug 2007, at 11:03, Matthieu Brucher wrote:




2007/8/21, Ged <gerard.murphy at amteus.com>: 

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.


In this case, I have to say that I have the same problem as the one you
have. If I commit to one of my branches, the slave that is on the trunk is
started. I tried to use the 'branch' argument instead of 'defaultBranch',
but it didn't work. 

Matthieu


-------------------------------------------------------------------------
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




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/6ffa4792/attachment.html>