[Buildbot-devel] Multiple change sources and scheduler issues

[Bailey, Darragh]

> -----Original Message-----
> From: buildbot-devel-bounces at lists.sourceforge.net [mailto:buildbot-devel-
> bounces at lists.sourceforge.net] On Behalf Of Dustin J. Mitchell
> Sent: 01 July 2008 15:28
> To: Duncan Ferguson
> Cc: buildbot-devel at lists.sourceforge.net
> Subject: Re: [Buildbot-devel] Multiple change sources and scheduler issues
>
> On Tue, Jul 1, 2008 at 8:34 AM, Duncan Ferguson
> <duncan.ferguson at altinity.com> wrote:
> > I have set up my buildbot v0.77 with a number of change sources and
> > Schedulers.  The problem I have is that when a change is detected all
> > schedulers are triggered, not just the one configured for the
> > particular svn repository.
>
> This is a shortcoming of the current buildbot architecture.  The only
> workaround I know is to run multiple buildmaster processes.  That's
> what we do.  I've been toying with the idea of running multiple
> BuildMaster services inside a single application (by futzing with the
> buildbot.tac), but that's a pretty awful hack, and still requires each
> slave machine to run a buildslave instance for each buildmaster.
>
> We're about to add a half-dozen additional buildmasters, and each
> buildmaster process already has a virtual size of 0.5G, so I'm a
> little worried about this issue, too :)
>
> Dustin
>

Could use of branch & fileIsImportant not be used here to avoid hear to avoid triggering on changes from additional sources. That's of course assuming you don't have branches/paths in the different repositories that are common.


--
Regards,
Darragh Bailey

Systems Software Engineer
Hewlett Packard Galway Ltd.
+353 91 75-4674

Postal Address:    Hewlett Packard Galway Limited, Ballybrit Business Park, Galway
Registered Office: Hewlett Packard Galway Limited, 63-74 Sir John Rogerson's Quay Dublin 2
Registered Number: 361933

_______________________________________________
The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender.
To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL".