You can override the "base_repo" and "base_branch" field in your
config to point to whatever upstream repository you want to track, see
http://wiki.sagemath.org/buildbot/details.
On Thu, Mar 6, 2014 at 2:04 AM, Nathann Cohen wrote:
>> Or even better sage -i
>> http://sage.math.washington.edu/home
> Or even better sage -i
> http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.1.spkg
HMm O_o
I just noticed that the "current branch" on the version of Sage on which I
installed the patchbot is not trac/develop anymore but a patchbot-specific
thing... Does that mean I can't work
Or even better sage -i
http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.1.spkg
On Wed, Mar 5, 2014 at 8:40 AM, Nathann Cohen wrote:
>> ~/sage> ./sage -patchbot
>> /home/ralf/sage/src/bin/sage: line 751:
>> /home/ralf/sage/local/bin/patchbot/patchbot.py: No such file or directory
>
> ~/sage> ./sage -patchbot
> /home/ralf/sage/src/bin/sage: line 751:
> /home/ralf/sage/local/bin/patchbot/patchbot.py: No such file or directory
>
> this is 6.2.base3
sage -i patchbot
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To un
On Wednesday, March 5, 2014 10:22:05 AM UTC+1, Robert Bradshaw wrote:
>
> compute resources to run the patchbot, just take build a copy of sage
> and run "./sage -patchbot" and it'll start testing tickets.
>
~/sage> ./sage -patchbot
/home/ralf/sage/src/bin/sage: line 751:
/home/ralf/sage/local/b
Y !
Of course the patchbot relies on people actually volunteering their
> compute resources to run the patchbot, just take build a copy of sage
> and run "./sage -patchbot" and it'll start testing tickets.
>
H I did not know that O_O;;;
I may not have been paying much attention
On Mon, Mar 3, 2014 at 2:45 AM, Frédéric Chapoton wrote:
> Hello,
>
> it seems that the patchbot has not really digested the git transition.
I converted it to use the new git format, which is even better as it
now knows exactly what to test and can even do spkgs, and
"non-sage-lib" patches.
Of c
On Mon, Mar 3, 2014 at 3:04 AM, Volker Braun wrote:
> There was some attempt to replace it with Jenkins at SD56, but I don't
> know how how far that progressed. Since the changeset information is now
> easily accessible through git it would make sense to replace it with a more
> run-of-the-mill c
There was some attempt to replace it with Jenkins at SD56, but I don't know
how how far that progressed. Since the changeset information is now easily
accessible through git it would make sense to replace it with a more
run-of-the-mill continuous integration tool.
On Monday, March 3, 2014 10
Hello,
it seems that the patchbot has not really digested the git transition. I
would be happy to see it back, as it was very useful in the development
process in the mercurial era.
To modify the patchbot, you have to clone from here
https://github.com/robertwb/sage-patchbot
and then propose
10 matches
Mail list logo
