Difference between revisions of "Buildbot"

Revision as of 07:59, 22 June 2010

A buildbot is now deployed for OpenOffice.org. http://termite.services.openoffice.org/

The Buildbot adaption for OOo is done in a separate project: http://code.google.com/p/ootermite/

From the Buildbot README: http://buildbot.sourceforge.net/

The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve.

The OOTermite buildbots are also designd to report their results to the OpenOffice.org Tinderbox system to allow combining efforts.

How to start a build

• Visit http://termite.services.openoffice.org/buildbot/
• Choose a machine you want to build on, and click on it
• Fill in the Your name, Reason for build, Branch to build (just the CWS name)
• If you want to have the resulting installation sets, check Install Set
• Press Force Build
• Wait until the installation sets appear in http://termite.services.openoffice.org/install_sets/ (if you wanted them)

If your build breaks it may be the Buildbot's fault as they are not perfect. If you are unsure feel free to contact the Buildslave's maintainer (contact address on the Builder's overview page). Generally speaking if the corresponding MWS builds fine a CWS break is the CWS' fault.

Slave system configurations

The Buildbot slaves do not build agains a specific baseline as they have varying operating systems and compilers. This was done by intention because we want as different systems as possible to get the OOo code robust and portable. You can of course use the builds for QAing, but do not espect reproducable results.

Nevertheless, a developer must know the exact configure parameters and environment information when inspecting a build break. These information should be available through this page. The used configure call can be always obtained through a recent build log, but is summarized here for convenience.