On Dec 8, 5:35 am, Simon King wrote:
> How case and noise resistant is the buildbot?
...
> And what about an indentation?
...
As far as I can tell, casing and spacing should both be irrelevant --
the functions "extract_patches" and "extract_depends_on" (from trac.py
in the buildbot source) bot
PS:
On 8 Dez., 11:22, Robert Bradshaw
wrote:
> Just have a line that says "depends on #8807 #10318"
How case and noise resistant is the buildbot?
E.g., above, you advised `put a line in any comment that says "Apply
foo.diff"` - upper case. Here you advise "depends" - lower case.
By "a line in
Hi Robert,
On 8 Dez., 11:22, Robert Bradshaw
wrote:
> Just have a line that says "depends on #8807 #10318"
Thank you!
Cheers,
Simon
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
On Wed, Dec 8, 2010 at 2:06 AM, Simon King wrote:
> Hi!
>
> Admittedly I did not follow the development of the buildbot.
>
> Am I right that it takes trac ticket, applies the patches and then
> tests? That would indeed be awesome.
>
> But how can one explain dependencies to the build bot. Concrete
Hi!
Admittedly I did not follow the development of the buildbot.
Am I right that it takes trac ticket, applies the patches and then
tests? That would indeed be awesome.
But how can one explain dependencies to the build bot. Concrete
example: How can I achieve that the buildbot first applies the
On Wed, Dec 8, 2010 at 12:54 AM, Johan S. R. Nielsen
wrote:
> Wow, this is really cool! Great work! Also, great plans for ways to
> let people run their own buildbots, hooked up to the central server.
> With customisation so ones own patches will be prioritised whenever
> needed, hopefully a lot o
Wow, this is really cool! Great work! Also, great plans for ways to
let people run their own buildbots, hooked up to the central server.
With customisation so ones own patches will be prioritised whenever
needed, hopefully a lot of people will feel that it's really _easier_
for them to have a build
On 12/7/10 4:41 AM, Robert Bradshaw wrote:
That's an interesting idea, but it's not easy to expose that
information. The way it works is that a build slave requests a list of
tickets, rates them according to its own internal settings (which may
be different for each bot), and then starts on a tic
On Tue, Dec 7, 2010 at 2:41 AM, Robert Bradshaw
wrote:
> On Mon, Dec 6, 2010 at 8:43 PM, Niles wrote:
>>
>>
>> On Dec 6, 10:53 pm, Jason Grout wrote:
>>> Robert (and whoever else is working on the buildbot [1]),
>>>
>>> First of all, THANK YOU!!! This is amazing! I love how it is hooked up
>>>
On Mon, Dec 6, 2010 at 8:43 PM, Niles wrote:
>
>
> On Dec 6, 10:53 pm, Jason Grout wrote:
>> Robert (and whoever else is working on the buildbot [1]),
>>
>> First of all, THANK YOU!!! This is amazing! I love how it is hooked up
>> to show the status on trac.
>
> Indeed -- THANKS ! ! !
Your wel
On Dec 6, 10:53 pm, Jason Grout wrote:
> Robert (and whoever else is working on the buildbot [1]),
>
> First of all, THANK YOU!!! This is amazing! I love how it is hooked up
> to show the status on trac.
Indeed -- THANKS ! ! !
>
> Could we add building documentation to the things that it che
11 matches
Mail list logo
