Differences between revisions 1 and 11 (spanning 10 versions)
⇤ ← Revision 1 as of 2010-12-03 20:23:53 →
Size: 652
Editor: robertwb
Comment:
← Revision 11 as of 2011-06-27 07:08:35 → ⇥
Size: 2528
Editor: FrédéricChapoton
Comment: better formatting
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
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. 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 usually be able to to determine which attachments for a given Trac ticket to apply; when in doubt click on the swirly blob to see it's plan of action. If it is unable to figure out what to do, tell Patch Buildbot explicitly which patches to apply by writing something like 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. The list of attachments which will be applied on the next run are listed at the top of the buildbot report page for that ticket (the page you get by clicking on the swirly round icon at the top of the ticket description).

To tell Patch Buildbot about any ticket dependencies, populate the dependencies field with the ticket numbers and/or minimal sage version.

Only the devel repository has branches, so the patchbot is unable to apply and try out patches to extcode/scripts/etc.

=== Possible status ===

Patches can have the following status:

 * New (grey)

 * ApplyFailed (red) The patch could not be applied. This can be caused by conflicts with other patches or dependencies.

 * BuildFailed ()

 * TestsFailed (yellow) Some tests did not succeed. They can be found in the report of the bot.

 * PluginFailed (blue) Documentation and commit messages should be checked. See the report to see what is wrong.

 * TestsPassed (green) Everything is ok, as far as the bot can tell.

 * Pending (grey) The bot is currently running on this patch.

 * NoPatch () No patch has been uploaded to trac so far.

 * Spkg (purple) This is not related to a patch but to a spkg package.


=== Hints and tricks ===

Detecting which patches to apply are both performed by string searches on each line of the ticket, and are case insensitive.

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 usually be able to to determine which attachments for a given Trac ticket to apply; when in doubt click on the swirly blob to see it's plan of action. If it is unable to figure out what to do, tell Patch Buildbot explicitly which patches to apply by writing something like 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. The list of attachments which will be applied on the next run are listed at the top of the buildbot report page for that ticket (the page you get by clicking on the swirly round icon at the top of the ticket description).

To tell Patch Buildbot about any ticket dependencies, populate the dependencies field with the ticket numbers and/or minimal sage version.

Only the devel repository has branches, so the patchbot is unable to apply and try out patches to extcode/scripts/etc.

Possible status

Patches can have the following status:

  • New (grey)

  • ApplyFailed (red) The patch could not be applied. This can be caused by conflicts with other patches or dependencies.

  • BuildFailed ()

  • TestsFailed (yellow) Some tests did not succeed. They can be found in the report of the bot.

  • PluginFailed (blue) Documentation and commit messages should be checked. See the report to see what is wrong.

  • TestsPassed (green) Everything is ok, as far as the bot can tell.

  • Pending (grey) The bot is currently running on this patch.

  • NoPatch () No patch has been uploaded to trac so far.

  • Spkg (purple) This is not related to a patch but to a spkg package.

Hints and tricks

Detecting which patches to apply are both performed by string searches on each line of the ticket, and are case insensitive.