[Buildbot-devel] Ticket 176

[Axel Hecht]

That ticket only has theories so far. If you could provide a standalone
testcase, it might be easier to find someone to look into it. Not that I'm
volunteering.

Axel

2009/1/20 John Earl <jearl at airsource.co.uk>

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20090120/ea60b086/attachment.html>