|
Size: 3183
Comment: https for patchbot images
|
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 development releases) on a wide variety of machines. It 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 (Patchbot) == | |
| Line 9: | Line 8: |
| 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 (round icons at top right). You can help by running your own patchbot. See this [[buildbot/details|instruction page]] for installation and usage. This is still very much a work in progress; the latest version of the code lives 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. === Lists of reports === You can see the status of several tickets at the same time (replace xxxx by your user name) : For the tickets you participated in, see http://patchbot.sagemath.org/ticket/?base=develop&participant=xxxx For the tickets you authored, see http://patchbot.sagemath.org/ticket/?base=develop&author=xxxx === Ticket Status === The color of the report page icon indicates the status of the ticket. See the report page itself for more details. The possible statuses are: {{https://patchbot.sagemath.org/svg/New||width=48}} '''New''' {{https://patchbot.sagemath.org/svg/Pending||width=48}} '''Pending''' A patchbot is currently running on this ticket. The patchbot may have stopped if the ticket was deemed unsafe. {{https://patchbot.sagemath.org/svg/TestsPassed||width=48}} '''!TestsPassed''' Everything is okay, as far as a patchbot can tell. {{https://patchbot.sagemath.org/svg/ApplyFailed||width=48}} '''!ApplyFailed''' The branch could not be applied. This can be caused by conflicts with other branches or dependencies. Try rebase your branch on the latest develop branch. {{https://patchbot.sagemath.org/svg/BuildFailed||width=48}} '''!BuildFailed''' The branch can be applied, but sage failed to build, due to errors in the code. Check the code. {{https://patchbot.sagemath.org/svg/TestsFailed||width=48}} '''!TestsFailed''' One or more tests did not succeed. {{https://patchbot.sagemath.org/svg/PluginFailed||width=48}} '''!PluginFailed''' Tests have been successfully done, but plugins have found some problems. {{https://patchbot.sagemath.org/svg/PluginOnlyFailed||width=48}} '''!PluginOnlyFailed''' Plugin have found some problems. Tests have not been made. {{https://patchbot.sagemath.org/svg/PluginOnly||width=48}} '''!PluginOnly''' Plugins have found no problem. Tests have not been made. {{https://patchbot.sagemath.org/svg/NoPatch||width=48}} '''!NoPatch''' No branch has been uploaded to Trac so far. The patchbot has nothing to do. {{https://patchbot.sagemath.org/svg/Spkg||width=48}} '''Spkg''' This is related to an spkg. The patchbot will only check the spkg installation. === Hints and tricks === * To rerun tests (even though the branch was 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.
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