Version 57 (modified by ashcrow, 12 years ago) (diff)


Welcome to 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.

The overall goal is to reduce tree breakage and provide a platform to run tests or code-quality checks that are too annoying or pedantic for any human to waste their time with. Developers get immediate (and potentially public) feedback about their changes, encouraging them to be more careful about testing before checkin.

You might like to look at some ScreenShots.


The current release is buildbot-0.7.9, made on September 16th, 2008: tgz (sig), zip (sig)

  • please read the NEWS file if you are upgrading from a previous release: it contains important information about compatibility and changes you must make to your configuration file
  • From Source:
  • With setuptools: run easy_install buildbot
  • Debian Users: install the 'buildbot' package . The current debian stable release ("etch") has 0.7.4, but there is a newer version in the 'unstable' or 'testing' distribution.
  • Ubuntu Users: install the 'buildbot' package from the Dapper 'universe' section (version 0.7.2 in dapper, 0.7.4 in edgy, 0.7.5 in feisty). (thanks to Matthias Klose for making both of these debian versions happen!). For newer versions, look for backports or install from source.
  • SUSE Users: Marcus Rueckert has made SUSE RPMs available at . There is also user documentation available.
  • Fedora Users: install the 'buildbot' package via yum ( "yum install buildbot" )
  • Darwin Users: run port install buildbot (thanks to Olivier Bonnet for making this happen!)
  • Fink Users (Mac OS X 10.4 and later): run "fink install buildbot-py25"
  • Solaris Users: you have to install buildbot from source yourself, but Matthew Flanagan has written a Solaris 10 SMF manifest which will help automatically launch the buildmaster or buildslave as a Solaris service.
  • Other RPM based distributions: see Building RPMs to produce RPMs for your Linux distribution, including RHEL and CentOS.


  • The README file contains an overview.
  • The User's Manual contains complete documentation.
  • The API Reference may be useful when writing the configuration file: the various Steps and Schedulers are documented there.
  • Recent changes for each release are summarized in the NEWS file, while the complete details are in the ChangeLog.
  • The Buildbot was first announced at PyCon 2003, where I delivered a paper along with some slides.
  • BuildbotAndTrac describes some ways to combine a Buildbot with a Trac instance.
  • Using launchd on Mac OS X to manage buildbot.



Getting Code



The beginning sketches of what may become Buildbot-1.0 are at BuildbotOneOh?.

Success Stories

Buildbots are installed in at least 100 sites all over the world. Users have submitted pointers to the SuccessStories page, so you can get a feel for how Buildbot is being used.

Install a buildbot today and add your name!

Also, there are sometime jobs that specifically target Buildbot pros. If you're a Buildbot fan and looking for employment, check out the BuildBotJobs page.


Many thanks to for hosting the buildbot's SourceForge Project Page for all these years. Logo

The original TracStartingPage was moved away.

If you'd like to edit these pages, please use the "Register" link at the top right corner of this page to create an account. I'd appreciate it if you'd add a useable email address when you do so (using the "Settings" link). If you do, you'll receive email when tickets that you have filed are updated or closed, and you can add your name as a cc: on tickets that you're interested in.