|
Size: 1056
Comment: tell Patch Buildbot which attachments to apply for a given ticket
|
Size: 374
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Sage has two build bots. | == The Sage Release Buildbot == |
| Line 3: | Line 3: |
| == Release Buildbot == | The buildbot builds entire tarballs (''e.g.'' all the development releases) on a wide variety of machines. It can be found at http://build.sagemath.org. |
| Line 5: | Line 5: |
| 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/ . | This is using the continuous integration framework of http://buildbot.net/ |
| Line 7: | Line 7: |
| == Patch Buildbot == | |
| Line 9: | Line 8: |
| 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 === |
'''NOTE:''' If you are looking for instructions to run a patchbot, see [[patchbot|the patchbot page]] |
The Sage Release Buildbot
The buildbot builds entire tarballs (e.g. all the development releases) on a wide variety of machines. It can be found at http://build.sagemath.org.
This is using the continuous integration framework of http://buildbot.net/
NOTE: If you are looking for instructions to run a patchbot, see the patchbot page