Tim Peters wrote: > Someone sets up a "buildbot master" That's what I now did: http://www.python.org/dev/buildbot/ I'm not quite sure on a number of concepts: should there be multiple "slaves" per "builder"? Should I have multiple factories? How should I pass build-machine specific information (like: what compiler to use) in the master, or is that a slave thing? How should I deal with branches? Anyhow, I created two "builders", both with the same "slave", on sparc-sun-solaris2.10, 32-bit mode, gcc. The "python-full" builder does "svn export", whereas the "python-quick" builder does "svn update". Each of these is associated with an AnyBranchScheduler, for both 'trunk' and 'tags/release24-maint'. Not sure whether this means that the 2.4 release branch will ever be built (as the SVN steps have a defaultBranch of "trunk"). If anybody wants to contribute additional builders, or has ideas for organizing this all, please let me know. Regards, Martin
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