Buildbot Steps

From Apache OpenOffice Wiki
Revision as of 12:58, 11 August 2006 by Dkeskar (Talk | contribs)

Jump to: navigation, search

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.


Buildbot Requirements

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:anonymous@anoncvs.gnome.org:/cvs/gnome login
no password
cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co ooo-build/scratch/buildbot/buildbot-0.7.3

Installing the Buildbot

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

"buildbot --version"

Setting up the Buildbot

  1. Make a buildbot directory on the machine at an appropriate place.
    • The full path name for this directory is hereinafter referred to as slavedir.
mkdir buildbot_ooo
  1. Run the buildbot command to create a build slave:
buildbot slave ''slavedir'' ''MASTERHOST'':''PORT'' ''SLAVENAME'' ''PASSWORD''
    • where
  1. 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.
  2. Checkout some OO build specific scripts from http://cvs.gnome.org/viewcvs/ooo-build/scratch/buildbot/slave/
cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome login
no password
cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co ooo-build/scratch/buildbot/slave
    • copy these files to slavedir
    • 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.

Email botmaster admin

  1. Once all the above steps are done, You need to email buildmaster administrator 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
  1. Once buildmaster administrator receives this above information, he will add your buildslave to buildfarm and then your slave will become OOBuildSlave and will be listed on buildmaster status page [1]
Personal tools