On 7/22/06, "Martin v. Löwis" <martin at v.loewis.de> wrote: > > Grig Gheorghiu wrote: > > As I said earlier: If you need some kind of post-commit > > trigger on the python repository to trigger a build, just > > let me know. We currently use a more-or-less plain > > svn_buildbot.py to trigger our own builds. > > > > Wouldn't that put too much of a burden on the python core build system? > > It would have to be aware of all the buildslaves running specific > projects. > > If there is a single "community buildbot", then no. In any case, it's > primarily administrative overhead, not so much cycles. python.org does > so many things simultaneously, making it trigger an additional build > remotely doesn't hurt. > > > I was thinking about having a dedicated buildmaster machine, such as the > > one Neal says he already has, and configure that machine to coordinate a > > small army of buildslaves which will be contributed for people > > interested in this effort. > > Right. You still need to find out when to rebuild, and getting triggers > from the source repositories is likely the easiest solution. 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 python.org is not too great, we can do what you suggested. Grig -- http://agiletesting.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060722/b7d1a491/attachment.htm
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4