Come join the collective! Bots for new platforms or adding bots for for existing platforms will increase the build capabilities available, and are therefore much appreciated.
What you need is a reasonably fast machine, with decent RAM and disk, and of course an Internet connection. It might be easier to first set up the openoffice build environment on this machine.
The Buildbot requires:
- Python 2.3 or later: http://www.python.org
- Twisted: http://twistedmatrix.com - most recent version is recommended. You'll need at least "Twisted" (the core package), and you'll also want TwistedMail, TwistedWeb, and TwistedWords.
- Note: For Twisted, you first need to install Zope.
Getting the OpenOffice Buildbot
The Buildbot has been customized for Openoffice.org builds. Please checkout buildbot-0.7.3 from Gnome CVS.
cvs -z3 -d :pserver:email@example.com:/cvs/gnome login no password cvs -z3 -d :pserver:firstname.lastname@example.org:/cvs/gnome co ooo-build/buildbot
Installing the Buildbot
- Detailed instuctions are at http://buildbot.sourceforge.net/manual-0.7.3.html#Requirements
- The install may need to be to run as root (su).
After all requirements are met, install buildbot by running following commands in buildbot directory.
python setup.py build python setup.py install
Test installation is proper by running the command
- Install is OK if you see the version information for Buildbot and Twisted.
- Errors such as 'no such command' or "ImportError" means something went wrong.
- Note: For more detailed instuctions see http://buildbot.sourceforge.net/manual-0.7.3.html#Installing-the-code
Setting up the Buildbot
Make a buildbot directory on the machine at an appropriate place.
- The full path name for this directory is hereinafter referred to as slavedir.
Run the buildbot command to create a build slave:
buildbot slave ''slavedir'' ooo-staging.osuosl.org:9989 ''SLAVENAME'' ''PASSWORD''
- Choose a SLAVENAME and PASSWORD and report them to botmaster administrator
- For more detailed instuctions see http://buildbot.sourceforge.net/manual-0.7.3.html#Creating-a-buildslave
- For additional creation options see http://buildbot.sourceforge.net/manual-0.7.3.html#Buildslave-Options
Fill in the hostinfo files
- slavedir/info/admin should contain your name and email address. This is the buildslave admin address
- slavedir/info/host should be filled with a brief description of the host. For example: OS, version, memory size, CPU speed, versions of relevant libraries installed, and finally the version of the buildbot code which is running on the machine.
Checkout some OO build specific scripts from http://cvs.gnome.org/viewcvs/ooo-build/scratch/buildbot/slave/
cvs -z3 -d :pserver:email@example.com:/cvs/gnome login no password cvs -z3 -d :pserver:firstname.lastname@example.org:/cvs/gnome co ooo-build/scratch/buildbot/slave
You will see the following files:
- buildbotget.pl - perl script for checking out OO source code from CVS
- buildoo - script to start OO build process. Note: You need to properly edit this file to meet your plateform requirement.
- smoketestoo - script to start OO smoke test after successful compliation. Note: You need to properly edit this file to meet your plateform requirement.
Please copy these files to slavedir
Email botmaster admin
Once all the above steps are done, please email botmaster administrators:
- pmadhav at openoffice.org
- mikeleib at openoffice.org
With the following information.
- SLAVENAME & PASSWORD : This is the same that you used while creating buildslave.
- slavedir (full path) e.g. /home/bbot/buildslave_ooostaging
- The configure command you are using for configuring OO on this build platform. e.g. ./configure --with-system-freetype
The botmaster administrator will then add your buildbot to the OpenOffice.org buildfarm. Your buildbot will then start carrying out OpenOffice.org builds in response to botmaster commands and will be listed on the status page at http://ooo-staging.osuosl.org:8010
Start the buildslave
Once buildmaster administrator configures your new buildslave, he will contact you about status. Once everything is OK then you can start your buildslave by running following command
buildbot start ''slavedir''
To stop buildslave anytime, please run
buildbot stop ''slavedir''