Size: 2573
Comment: missing colors added
|
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/ . == 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 (red) * 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 bot report. * TestsPassed (green) Everything is ok, as far as the bot can tell. * Pending (grey) The bot is currently running on this patch. * NoPatch (purple) No patch has been uploaded to trac so far. The bot has nothing to do. * Spkg (purple) This is not related to a patch but to a spkg package. The bot is not concerned. |
This is using the continuous integration framework of http://buildbot.net/ |
Line 47: | Line 8: |
=== Hints and tricks === Detecting which patches to apply are both performed by string searches on each line of the ticket, and are case insensitive. |
'''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