Get the Code

Buildbot has been through a number of version-control systems, but is currently a Git repository hosted at  GitHub:

 http://github.com/djmitche/buildbot

There are a few important branches here:

• master contains the latest development
• one-oh contains the latest work on BuildbotOneOh?, the next generation of buildbot.

If you're not a git whiz, you can download a tarball of this repository by clicking the "Download" link on the GitHub page.

Note that the Arch, Darcs, and CVS versions of the source are deprecated and no longer updated.

Develop a Patch

The best way to submit patches to Buildbot is using GitHub's forking mechanism. For details, see SubmittingPatches.

Writing Tests

See TowardBetterBuildbotTests.

Tips

• See RunningBuildbotWithVirtualEnv for hints on how to work on Buildbot using virtualenv
• FutureIdeas has some random thoughts on things that might make the Buildbot better.
• the MetaBuildbot tests Buildbot itself.
• Lately we've wanted an RcsTeminologyCrossReference so that different RCS users can converse intelligently.
• The beginning sketches of what was thought of as Buildbot-1.0 are at BuildbotOneOh?. It's something of a pipe dream.

What is this crazy Git stuff?

If you want to take the short way out, you can create an old-fashioned patch file with this simple recipe:

• Copy the most recent source:

  git clone git://github.com/djmitche/buildbot.git
  cd buildbot
  

• Hack
• Make a patch:

  git diff > my.patch
  

Notes

Notes for developers

• CuttingReleases

Notes from meetings

• Meeting29April2010

Current work

• JinjaBranch - replace internal html pasting code with templates