From Buzztard

[edit] Introduction

To check the builds for buzztard you can use the Buildbot system. With the help of such system many clients, called builbots, can build the project on several platforms.

In this mini HowTo we will guide you to setup the buildmaster and buildslave on one PC. This PC is the buildmaster and has its own buildslave to build the project.

[edit] Download and install

You can download the Buildbot system from sourceforge or use Gentoo which has an package for this.

Simple follow the instructions on how to install the buildbot script.

In the follwing sections we refer to the gentoo installation.

[edit] Create user

For safety you may create a user for your system. We call this user the builbot user and create this with our unix adminstration tool.

The buildbot master and slave deamon should run as this user. This user should also own all files related to the buildbot system.

[edit] Buildmaster

The buildmaster is the system which holds all informations about the several build slaves and to show the HTML page of the buildsystem.

[edit] Create buildmaster

The buildmaster should store the files in a directory called master directory. For our choice we use

~builbot/master/buzztard

To create the build master directory layout with sample files you can choose the following command

buildbot create-master ~builbot/master/buzztard

[edit] Configure the buildmaster

The configuration file for the buildmaster can be found in the buildmaster directory:

~builbot/master/buzztard/master.cfg

There is a sample after creating the buildmaster called master.cfg.sample which is a good starting point to configure the buildmaster.

[edit] Setup project information

Here you can setup the project name, the url where the buildmaster can be found and the project URL.

Set the project name:

c['projectName'] = "Buzztards buildbot"

Set the project backlink URL:

c['projectURL'] = "http://buzztard.org/"

Set the buildmaster URL:

c['buildbotURL'] = "http://141.57.8.70:8010/"

Under this URL the HTML page of the buildmaster can be found. Use you own IP adress and port where small HTTP server of the buildmaster system should stay on.

[edit] Setup connectivity for the slaves

In this step we configure our buildslave which can be connect to the buildmaster.

You can configure here more than once:

c['bots'] = [("firstslave", "slavepasswd")]

Where firstslave is the name of the first slave (you can see it as the slave user name). The slavepasswd is the password for this slave.

[edit] Buildslave

[edit] Problems

we don't have a good working way to trigger builds from cvs commits on sf.net repository (we can't install the buildbot software there to do buildbot sendchange)
the irc bot fails to connect to quakenet.org, but works on e.g. freenode.org
the irc bot does not report build results automatically