so... (tada.wav) Vanilla builds alrite on one slave. Nest step would be uploading the file, this can be done internally, just tell me please which file or directory is the actual build? And... how do we make a package with the Vanilla source? Sorry I never built it myself.
Some more questions that came up meanwhile: Shall we update or copy the source each time? (see http://buildbot.net/buildbot/docs/latest/Source-Checkout.html) Do we need --enable-jack to configure Vanilla (after autogen)?

Andras

The way that this would be super useful is if buildbot builds after every commit to SVN or git.  It looks like SVN polling support is built-in


For git, it supports checkout, but there are some external scripts for polling:

.hc

yes, git is more cumbersome when it comes to polling, so i will work this out with daily builds and see the polling stuff after. the older buildbot version also has some limitations in this direction.

I think we can start with SVN since that should be easier.  If that works nicely, then we can struggle to get git polling working.  

Alrite. My box may fall out then, because i cannot handle so many build cycles per day, or i'll try to find a way to limit it to one build cycle on 'civilian' boxes like mine.

Ah yes, that makes sense.  I was thinking the full time machines.


Or a Dell Zino for 250 USD, its 64-bit and runs Debian/Ubuntu nicely. 

http://www.dell.com/us/en/home/desktops/inspiron-zino-hd/pd.aspx?refid=inspiron-zino-hd&cs=19&s=dhs

 
Cool. The X2100 is basically identical to the Ultra20 i have, it's a Tyan main board with Opteron - and runs Debian/Ubuntu nicely :o)

How do we raise the funds? Is there an established way, or idea how to do it?

Andras