Setting up a Try Server

The Try Server consists of a few parts

• Web interface (mozilla/webtools/buildbot-try)
• Patch downloading/insertion script (mozilla/webtools/buildbot-try)
• Buildbot master/slaves setup. (mozilla/tools/buildbot-configs/tryserver and mozilla/tools/buildbotcustom)

At Mozilla, we run the web interface on one machine and the other parts on a separate network but they can both be run on the same machine if you'd like.

Setting up the Web Interface

The web interface depends on Perl w/ the LWP module. This should come with your standard Perl installation.

1. Checkout the buildbot-try directory somewhere on your webserver:

cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -d buildbot-try mozilla/webtools/buildbot-try

</ol>

Setting up the Buildbot Master

The Try Server Buildbot requires Buildbot 0.7.5 or higher. All of the necessary files are in CVS.

1. Checkout the tryserver Buildbot configs and buildbotcustom module from CVS onto your Buildbot master

cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -d tryserver mozilla/tools/buildbot-configs/tryserver
cd tryserver
cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -d buildbotcustom mozilla/tools/buildbotcustom
cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -d processor mozilla/webtools/buildbot-try/processchanges.pl
mv processor/processchanges.pl
rm -rf processor

2. Edit the variables in processchanges.pl to match your web server/buildbot configuration.
3. Create a buildbot master in your 'tryserver' directory.

cd tryserver
buildbot create-master .

4. Connect one or more slaves to your master

Using your Try Server

Just use your web browser to submit your changes!

You can set up processchanges.pl to be run as a cronjob. Running it every minute or two is OK. If it's just for personal use you may or may not care about it running automatically. To force it to look for new changes you can simply run 'processchanges.pl'.