Differences between revisions 3 and 89 (spanning 86 versions)
⇤ ← Revision 3 as of 2013-10-21 08:21:48 →
Size: 1583
Editor: chapoton
Comment: + more
← Revision 89 as of 2017-02-02 17:24:53 → ⇥
Size: 0
Editor: mrennekamp
Comment: move to [[buildbot]]
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
There are (at least) two ways to run your own private patchbot, that will report its results to the trac server.

In any case, it is better to have disk space available and a powerful enough machine.

== Run on all tickets ==

You can let the patchbot choose the tickets it will run on.

 * Install the patchbot using "sage -i patchbot"

 * Run the patchbot using "sage -patchbot"

I will run forever, as long as it finds a ticket to work on. Tickets are only considered if their authors are trusted.

== Run on chosen tickets ==

Here is a proposal on how to use the patchbot only on tickets you want to work on.

'''Warning''': this works for a mercurial setting, not tested for the new git setting.

 * install the latest sage development release (download from http://www.sagemath.org/download-latest.html and make)

 * install the latest patchbot (clone from http://github.com/robertwb/sage-patchbot)

 * in a terminal, inside your_sage_home_dir, "./sage -clone 0"

 * in a terminal: "cd sage-patchbot/src" then "ipython"

 * in ipython, "from patchbot import Patchbot", then "P = Patchbot('your_sage_home_dir',"http://patchbot.sagemath.org/",None,plugin_only=True)" or "P = Patchbot('your_sage_home_dir',"http://patchbot.sagemath.org/",None)"

The first one will only run the plugins (much faster), the second one will run all the tests (much slower).

 * Then choose your favorite ticket number N and "P.test_a_ticket(N)"

It is important that sage is in its initial state when running the patchbot (sage-main branch with no patch applied).