Differences between revisions 1 and 3 (spanning 2 versions)
Revision 1 as of 2010-12-03 20:23:53
Size: 652
Editor: robertwb
Comment:
Revision 3 as of 2010-12-04 16:35:32
Size: 1056
Editor: NilesJohnson
Comment: tell Patch Buildbot which attachments to apply for a given ticket
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:

=== Usage ===

Patch Buildbot will try to determine which attachments for a given Trac ticket to apply. To tell Patch Buildbot explicitly which patches to apply, write the following in any comment:

    Apply foo.patch, foo2.patch

This will "reset" the patch list at that point. Any subsequently added patches will
get (semi-intellegently) appended to the list.

=== Hints and tricks ===

Sage has two build bots.

Release Buildbot

The first builds entire tarballs (e.g. all the alphas) on a wide variety of machines, and can be found at http://build.sagemath.org/sage/ .

Patch Buildbot

The second pulls and applies patches from trac and can be found at http://sage.math.washington.edu:21100/ticket/ or from links on the individual trac tickets. This is still very much a work in progress, but the latest version of the code lives at http://sage.math.washington.edu/home/robertwb/buildbot/bot/ . Eventually this will get moved into Sage where it can be edited using the standard procedures and more widely deployed.

Usage

Patch Buildbot will try to determine which attachments for a given Trac ticket to apply. To tell Patch Buildbot explicitly which patches to apply, write the following in any comment:

  • Apply foo.patch, foo2.patch

This will "reset" the patch list at that point. Any subsequently added patches will get (semi-intellegently) appended to the list.

Hints and tricks