|
Size: 1056
Comment: tell Patch Buildbot which attachments to apply for a given ticket
|
Size: 1579
Comment: more details about ticket dependencies
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| 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: | 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 something like the following in any comment: |
| Line 18: | Line 18: |
| get (semi-intellegently) appended to the list. | 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, write something like the following in any comment: Depends on #1719 |
| Line 21: | Line 25: |
Detecting ticket dependencies and 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 try to determine which attachments for a given Trac ticket to apply. To tell Patch Buildbot explicitly which patches to apply, write 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, write something like the following in any comment:
- Depends on #1719
Hints and tricks
Detecting ticket dependencies and which patches to apply are both performed by string searches on each line of the ticket, and are case insensitive.