This page gives detailed information about how Continuous Integration (BuildBot) is involved in the overall Twisted development process.

BuildBot provides a web interface (sometimes called the "web status") <>. This interface can be used to view recently results or to trigger new builds.

BuildBot operates automatically in many cases. It builds every revision of trunk as soon as it is committed. For feature branches, builds must be triggered explicitly.

Read Access

"Latest Builds" on the front page is a link to the primary overview page for Twisted. From the "Latest Builds" (or "boxes-supported") view you can see the results of the last ten (or so) builds done by each builder (for "supported" builders only). Each builder is given a row in the table. Each column in the table roughly (but not exactly) corresponds to a particular revision of the code which was built. Therefore, the common requirement of determining whether the most recent version of the code works on all supported builders (roughly corresponding to "in all supported configurations" or "on all supported platforms") can be satisfied by looking at the leftmost column (excluding the builder label column) to see if it is completely green (indicating success) or not (red indicating failure, purple indicating an internal error, yellow indicating in-progress).

By default, only builds on the trunk branch are displayed. This can be modified by using the form at the top-right of the page (enter a branch name and you will see results only for that branch).

Write Access

After logging in, the web interface can be used to trigger new builds. This is useful during development to test changes on the various platforms and under the various configurations which Twisted considers "supported" (and therefore must have a completely passing ("green") test suite).

Credentials to log in to the web interface are available to any Twisted contributor, the username is "twisted" and the password is "matrix". Note that without Git commit access, though, it's not possible to test new code (because the code must be committed to a Git branch before BuildBot will execute it).

After logging in, the "View" form at the top-right of the "Latest Builds" page will gain a "Force" button. Enter a branch name and click "Force" in order to trigger a build. Feel free to do this as often as necessary to successfully implement a change. Try not to do it more often than necessary, particularly when other developers are trying to test out their changes: build resources are limited and everyone needs to share them.

Looking At A Ticket

If the “branch” field is populated on a Trac ticket page, several useful links will be derived from it, including "diff" (a plain-text diff), "github" (a link to a pretty comparison of the branch as merged into trunk on github), "buildbot" (a link to the builds for that branch), and "log" (a list of commits the branch comprises in the Trac source browser). The "branch" field should be populated automatically from a commit hook, but if it's not for some reason, you can manually fix it by editing the "branch" field to contain a value like "branches/branchname-5000".

If you click on the "buildbot" link, you'll see the most recent builds for that ticket, and if you are logged in to the buildbot, you can click the "force" button at the top right to force a build for that branch. This should be easier than manually copying and pasting the branch name.

Using Buildbot Helpers

  1. Get force-build.
    • pip install twisted-dev-tools to get
  2. Run the script on your branch with force-build [-b <branch name>] [-t <tests>] [--comment '<Comment>']
    • The current branch will be used by default, if you are using a GitMirror
    • Otherwise, /branches/ will be added automically, if it is not present.
  3. Look at the results at the URL<branch name>
    • This link is printed by force-build
    • The latest trunk build can been viewed at
Last modified 6 years ago Last modified on 05/17/16 08:35:50