Getting the buildbot source

Quick links

Other sites

Except as otherwise noted, the content of this page is licensed under a Creative Commons Attribution 2.5 license, and examples are licensed under the BSD License.

For Developers‎ > ‎Testing and infrastructure‎ > ‎Chromium build infrastructure‎ > ‎

Contents

1 Whole raw sources
1. 1.1 Private data
2 Buildbot instance types
3 Configuring your buildbot instances

Whole raw sources

Our continuous build infrastructure is based on buildbot, written in python. All the Python scripts, HTML, and Javascript that the buildbot uses is also kept in the Subversion repository. Check out the whole set with:

mkdir tools && cd tools

gclient config http://src.chromium.org/chrome/trunk/tools/build

gclient sync

For quick hacking, a simple checkout is fine enough:

svn co svn://svn.chromium.org/chrome/trunk/tools/build


If you do not have a SVN account:

svn co http://src.chromium.org/chrome/trunk/tools/build

Private data

The build scripts assume that any private bits are in build_internal, beside build. So a private configuration file would be a build_internal/site_config/config_private.py.

Buildbot instance types

Description of some of the masters:

master.chromiumos: ChromiumOS continuous build.
master.chromium: Our main continuous buildbot.
master.chromium.fyi: Our For Your Information waterfall. Contains configurations and slaves that are expected to break.
master.experimental: At minimal buildbot master to play with. That's the best configuration to learn how to play with buildbot.
master.client.nacl: Native Client buildbot.
master.tryserver.chromium: Our try server. Permits testing patches before committing.
master.tryserver.nacl: Equivalent for NaCl.

Configuring your buildbot instances

Next step, configuring the buildbot.

Subpages (5): 1. Configuring/setting up the buildbot instances 2. Running a buildbot instance 3. Forking your buildbot 4. Maintain your Buildbot infrastructure 5. Buildbot Tips and Tricks

Comments