From Apache OpenOffice Wiki
Revision as of 05:52, 12 October 2006 by Mikeleib (Talk | contribs)

Jump to: navigation, search

A buildbot is now deployed for

From the Buildbot README:

Please see how you can add your own buildbot!

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. Buildbot

The Buildbot will:

  • Build CWS/SVN branches on multiple platforms and make output available to developers
  • Generate and make available install sets for multiple platforms
  • Run tests (smoketest, performance tests, etc.) and make test reports available for tracking and regression.

Buildbot vs. Tinderbox

Currently, there is a Tinderbox. In fact, the Buildbot uses or adapts several Tinderbox scripts. The Buildbot provides several advantages:

  • At-a-glance, customizable statusboard
  • Flexible, modular, extensible framework
  • Bots can be commanded and coordinated from the botmaster

Both Buildbots and Tinderboxes are easy to setup and can be behind the firewall. Thanks to Cloph for reminding about the similarities.

Deployment & Hardware

Currently, the botmaster and several buildbots are hosted at OSU-OSL ( Additional machines will be added to the pool. Sun QA/RE plans to host a Solaris bot.


Many buildbot based projects dedicate groups of bots to specific code branches. Thus, for example, checkins to HEAD will automatically trigger the associated pool of machines and the changes built, tested on multiple platforms. See for example:

However, this is impractical for due the numericity of branches (CWS'es). Instead, we focus on creating a reasonable sized pool of machines for each platform/variant, with flexible build policies (see below).

Currently, bots build for:

  • debian
  • suse 10.0
  • suse 10.1 (jre and gij)
  • suse 7.3 (several)
  • windows xp (3+)


The botmaster will schedule builds based on policies that take into account the pool size, machine status and build time. When a bot is busy doing a build, additional requests are automatically queued.

  • At UTC 0200 + random() build HEAD
  • At milestone release build milestone
  • Build manually requested CWS or milestone
  • Build automatically selected CWS


  • When no CWS is provided --> checkout HEAD - Done
  • Summaries - Done
    • tail, warnings, errors, summary log like tinderbox
    • error - show before/after buffer (15, 5) and skip ... between errors
  • Deploy install-sets on bot-master - Done
  • Increase length of status page. - Done
  • Email notification of build result (fail, success, install, etc. with link to buildlogs)
    • Send mail to when finished. (add a hint on the request form) - Done
    • For CWS - send to CWS owner (from EIS)
  • Fix smoke-test on some hosts
  • CWS-Oriented View - Done
    • Add header X axis (timeline)
    • Three different views - all, ready for QA, new
  • Buildslave info on slave web page
  • Scheduler to prioritize and distribute builds on various slaves
    • Collect changes by one user (settling) in one build
    • AllCVS mailing list listener to auto trigger build on commit notification
  • Header Row - provide number/link to last build (related to status)
  • Extra config switches field in force build form. Developers can specify some extra configure switches specific to there CWSs. - Done
  • Add suse 7.3 buildslave
  • Generate buildbot results as RSS feed for planetizing
  • For windows slaves, provide link to html build status page
  • UserId/Password verification for force build and stop buid


  • Prasad Madhav (pmadhav) deployed and customizes the buildbot
  • mikeleib, kaib, vq, dkeskar support and provide ideas
Personal tools