SpringLobby

How to setup a buildslave:

Make sure every step succeeds for you in the guides below. If any step fails, ask me (koshi) to help.

cd /tmp
git-clone git://springlobby.info/git/buildbot/springlobby.git
cd springlobby
mkdir build
cd build
cmake ..
make

The above is very near what the buildbot will do, so make sure it succeeds manually first, to make troubleshooting easier later.

(Note: until buildbot 0.80 hits package repositories it is recommended to install buildbot from source obtained via http://buildbot.net)
If you are on debian or ubuntu, do apt-get install buildbot. This takes care of the following tasks:

• install dependencies of buildbot
• create buildbot user (buildbot)
• create buildbot home dir (/var/lib/buildbot)
• create configuration file for the startup scripts (/etc/default/buildbot)
• create the startup scripts (/etc/init.d/buildbot)
  If you are on some other distro, ask for help.

• initialize buildslave (you need to contact me for SLAVENAME and PASSWORD)

sudo -u buildbot mkdir /var/lib/buildbot/slaves
sudo -u buildbot buildbot create-slave /var/lib/buildbot/slaves/springlobby springlobby.info:9989 SLAVENAME PASSWORD

Edit the following files:

BASEDIR/info/admin should contain your name and email address. This is the “buildslave admin address”, and will be visible from the build status page (so you may wish to munge it a bit if address-harvesting spambots are a concern).

BASEDIR/info/host should be filled with a brief description of the host: OS, version, memory size, CPU speed, versions of relevant libraries installed (wxWidgets), and finally the version of the buildbot code which is running the buildslave.

Add this to /etc/default/buildbot (if you are on something else than debian or ubuntu, ask for help)

BB_NUMBERr1=1
BB_NAMEr1="springlobby buildslave" 
BB_USERr1="buildbot" 
BB_BASEDIRr1="/var/lib/buildbot/slaves/springlobby" 
BB_OPTIONSr1="" 
BB_PREFIXCMDr1="nice" 

And finally run:

sudo /etc/init.d/buildbot start

Then go visit http://buildbot.springlobby.info/buildslaves to see that your slave connected.

If you could build multiple versions of wx widgets, that would help even more, so I can run the full test suite on your slave:

sudo apt-get install mingw32
cd /tmp
wget http://prdownloads.sourceforge.net/wxwindows/wxWidgets-2.8.7.tar.gz
tar xzf wxWidgets-2.8.7.tar.gz

cd wxWidgets-2.8.7
mkdir build-mingw build-linux
cd build-mingw
../configure --enable-unicode --prefix=/var/lib/buildbot/lib/mingw/wx/2.8 --host=i586-mingw32msvc --build=i586-linux
make
sudo -u buildbot make install
cd ..

cd build-linux
../configure --enable-unicode --prefix=/var/lib/buildbot/lib/linux/wx/2.8
make
sudo -u buildbot make install

cd /tmp
wget http://prdownloads.sourceforge.net/wxwindows/wxWidgets-2.6.4.tar.gz
tar xzf wxWidgets-2.6.4.tar.gz
cd wxWidgets-2.6.4
mkdir build-linux
cd build-linux
../configure --enable-unicode --prefix=/var/lib/buildbot/lib/linux/wx/2.6
make
sudo -u buildbot make install