[Buildbot-devel] Ticket 176

[Brian Fallik]

John,

That bug is also causing us grief.  Our solution was to replace
reconfig with stop and start.  Not very elegant but it works for us.

Thanks,
brian

On Tue, Jan 20, 2009 at 5:21 AM, John Earl <jearl at airsource.co.uk> wrote:
> Hi all,
>
> We have a lot of largely independent small projects, so we dynamically
> construct our buildbot configuration by scanning our repository for
> per-project build configuration scripts. Every time someone commits a
> change to one or creates a new branch that contains one, we trigger a
> reconfig on the master.
>
> This works great, but we're running into ticket 176 all the time as a
> result. From the comments on the ticket it looks like it's on hold for
> the moment. Any suggestions for a quick fix? Alternatively any hints on
> what to look at when I have time to spare to look at it would be useful.
>
> Cheers
>
> John
> --
> John Earl - Engineer
> Airsource Ltd
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>