|
Size: 3169
Comment: remove mercurial references
|
Size: 290
Comment: patchbot moved to its own page
|
| 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 development releases) on a wide variety of machines. It can be found at http://build.sagemath.org/sage/ . == Patch Buildbot == The second pulls and applies git branches from Trac and can be found at http://patchbot.sagemath.org/ or from links on the individual Trac tickets. This is still very much a work in progress; the latest version of the code lives at https://code.google.com/p/sage-buildbot/ (or at http://github.com/robertwb/sage-patchbot). Eventually this will get moved into Sage where it can be edited using the standard procedures and more widely deployed. See ticket http://trac.sagemath.org/sage_trac/ticket/12486. If you want to run a patchbot on your machine, see this [[buildbot/details|instruction page]]. === Lists of reports === You can see the status of several patches at the same time (replace xxxx by your user name) : For the patches you participated in, see http://patchbot.sagemath.org/ticket/?participant=xxxx For the patches you authored, see http://patchbot.sagemath.org/ticket/?author=xxxx === Patch Status === The color of the report page icon indicates the status of the patch. See the report page itself for more details. The possible statuses are: {{http://patchbot.sagemath.org/blob/New}} '''New''' {{http://patchbot.sagemath.org/blob/Pending}}* '''Pending''' A patchbot is currently running on this patch. {{http://patchbot.sagemath.org/blob/TestsPassed}} '''!TestsPassed''' Everything is okay, as far as a patchbot can tell. {{http://patchbot.sagemath.org/blob/ApplyFailed}} '''!ApplyFailed''' The patch could not be applied. This can be caused by conflicts with other patches or dependencies. {{http://patchbot.sagemath.org/blob/BuildFailed}} '''!BuildFailed''' The patch can be applied, but sage failed to build. {{http://patchbot.sagemath.org/blob/TestsFailed}} '''!TestsFailed''' One or more tests did not succeed. {{http://patchbot.sagemath.org/blob/PluginFailed}} '''!PluginFailed''' Documentation, commit messages and trailing whitespaces should be checked. {{http://patchbot.sagemath.org/blob/PluginOnlyFailed}} '''!PluginOnlyFailed''' Documentation, commit messages and trailing whitespaces should be checked. Tests have not been made. {{http://patchbot.sagemath.org/blob/PluginOnly}} '''!PluginOnly''' Only Documentation, commit messages and trailing whitespaces have been validated. Tests have not been made. {{http://patchbot.sagemath.org/blob/NoPatch}} '''!NoPatch''' No patch has been uploaded to Trac so far. The patchbot has nothing to do. {{http://patchbot.sagemath.org/blob/Spkg}} '''Spkg''' This is not related to a patch but to a spkg. The patchbot is not concerned. === Hints and tricks === * Detecting which patches to apply are both performed by string searches on each line of the ticket, and are case insensitive. * The patch list directive does not work in ticket descriptions. * To rerun tests (even though the patches to apply were not modified) add the kick parameter, e.g., http://patchbot.sagemath.org/ticket/12345/?kick |
'''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.
NOTE: If you are looking for instructions to run a patchbot, see the patchbot page