On 7/22/06, <b class="gmail_sendername">"Martin v. Löwis"</b> <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Grig Gheorghiu wrote:<br>> As I said earlier: If you need some kind of post-commit<br>> trigger on the python repository to trigger a build, just<br>> let me know. We currently use a more-or-less plain
<br>> svn_buildbot.py to trigger our own builds.<br>><br>> Wouldn't that put too much of a burden on the python core build system?<br>> It would have to be aware of all the buildslaves running specific projects.
<br><br>If there is a single "community buildbot", then no. In any case, it's<br>primarily administrative overhead, not so much cycles. <a href="http://python.org">python.org</a> does<br>so many things simultaneously, making it trigger an additional build
<br>remotely doesn't hurt.<br><br>> I was thinking about having a dedicated buildmaster machine, such as the<br>> one Neal says he already has, and configure that machine to coordinate a<br>> small army of buildslaves which will be contributed for people
<br>> interested in this effort.<br><br>Right. You still need to find out when to rebuild, and getting triggers<br>from the source repositories is likely the easiest solution.</blockquote><div><br><br>I see....I guess I was thinking about building periodically (every X hours or at time Y) as opposed to getting svn triggers on each check-in. But if, as you're saying, the overhead on
<a href="http://python.org">python.org</a> is not too great, we can do what you suggested.<br><br>Grig<br></div><br></div><br>-- <br><a href="http://agiletesting.blogspot.com">http://agiletesting.blogspot.com</a>