Sage has two build bots.
The first builds entire tarballs (e.g. all the development releases) on a wide variety of machines. It can be found at http://build.sagemath.org/sage/ .
The second pulls and applies patches from Trac and can be found at http://patchbot.sagemath.org/ or from links on the individual Trac tickets. This is still very much a work in progress; the latest version of the code lives at https://code.google.com/p/sage-buildbot/ . Eventually this will get moved into Sage where it can be edited using the standard procedures and more widely deployed. See ticket http://trac.sagemath.org/sage_trac/ticket/12486.
The Patch Buildbot automatically select patches (from the ticket attachments) to apply. Every Trac ticket has a Patch Buildbot report page, which is accessed by the swirly, round icon at the top of the ticket description. The report page lists the patches the buildbot chose. To override this choice, use the following directive in a ticket comment:
- Apply foo.patch, foo2.patch
Any subsequently added patches will be (semi-intelligently) appended to the list. To tell Patch Buildbot about any ticket dependencies, populate the dependencies field with the ticket number(s) and/or minimum Sage version.
Only the devel repository has branches, so the buildbot is unable to apply and try out patches to extcode/scripts/etc.
Lists of reports
You can see the status of several patches at the same time (replace xxxx by your user name) :
For the patches you participated in, see http://patchbot.sagemath.org/ticket/?participant=xxxx
For the patches you authored, see http://patchbot.sagemath.org/ticket/?author=xxxx
For the reports with respect to a given version of sage, see http://patchbot.sagemath.org/ticket/?base=5.x
These options can be combined using the separator &.
The color of the report page icon indicates the status of the patch. See the report page itself for more details. The possible statuses are:
Pending The bot is currently running on this patch.
TestsPassed Everything is okay, as far as the bot can tell.
ApplyFailed The patch could not be applied. This can be caused by conflicts with other patches or dependencies.
TestsFailed One or more tests did not succeed.
PluginFailed Documentation, commit messages and trailing whitespaces should be checked.
PluginOnlyFailed Documentation, commit messages and trailing whitespaces should be checked. Tests have not been made.
PluginOnly Only Documentation, commit messages and trailing whitespaces have been validated. Tests have not been made.
NoPatch No patch has been uploaded to Trac so far. The bot has nothing to do.
Spkg This is not related to a patch but to a spkg. The bot is not concerned.
Hints and tricks
- Detecting which patches to apply are both performed by string searches on each line of the ticket, and are case insensitive.
- The patch list directive does not work in ticket descriptions.
To rerun tests (even though the patches to apply were not modified) add the kick parameter, e.g., http://patchbot.sagemath.org/ticket/12345/?kick