[Sbcl-devel] SBCL buildbot // looking for buildslaves

[James Y K. <fo...@fu...>]

Hi, I set up a buildbot, an automated build tool, for SBCL at http:// 
sbcl.static.net/. It is setup to build, run tests (and report the  
outcome), and then build a binary and put it online after each  
commit. It will do this for every architecture with an online  
buildslave. I consider the auto-testing the main point of this, and  
the autobuilding of binary tarballs for every architecture a nice  
side-benefit.

I'd like to expand this buildbot to cover the rest of the  
architectures SBCL supports. Right now, I have only one, linux-x86.  
So, if you have a linux-x86_64, linux-powerpc, linux-sparc, linux- 
alpha, linux-mips, linux-mipsel, linux-hppa, darwin-x86, darwin- 
x86_64, darwin-powerpc, solaris-x86, solaris-sparc, freebsd-x86,  
freebsd-x86_64, netbsd-x86, openbsd-x86, or win32-x86 machine with  
some spare CPU cycles, please lend a hand. It only needs to be able  
to make a connection *outwards* to my machine (and the sourceforge  
CVS server), so NAT/firewalls are not a problem. I'll be so bold as  
to say that eventually, only those architectures which have  
buildslaves should actually be called "supported", because otherwise,  
clearly nobody cares about them. :)

I don't need a shell account on your machine, but I, and everyone who  
can commit changes to SBCL CVS that affect the build process will be  
able to run arbitrary commands on your machine with whichever UID you  
run the buildslave under. (which, of course, is not too much  
different than when you manually run "make.sh" without actually  
reading all the source code of SBCL first).

Please see <http://sbcl.static.net/helping.html> for some  
instructions on how to get setup. As, so far, nobody else has tried  
to use these instructions to setup a buildslave, there may be some  
issues, so let me know, I'll update them as necessary.

It doesn't currently send out emails, but (unless there's  
objections), I'd like to set it up to send an email whenever someone  
breaks a build. Do people read the use...@us...  
email addrs that the commit messages are from?

James