Re: [Lse-tech] Re: Minutes from OSDL talk at LSE call today

[Larry McVoy <lm@bitmover.com>]

On Thu, Dec 04, 2003 at 01:45:17PM -0800, cliff white wrote:
> On Wed, 3 Dec 2003 19:35:35 -0800
> Larry McVoy <lm@bitmover.com> wrote:
> 
> > On Wed, Dec 03, 2003 at 05:20:29PM -0800, Hanna Linder wrote:
> > > The Mozilla Tinderbox is based on CVS and can do fancy things with
> > > triggers. The kernel one is not as fancy because they are still
> > > working out issues with BK.
> > 
> > If we could get a list of these issues we'll try and see what we can do
> > to help.  My response has been a bit spotty lately, I've needed to take
> > some personal time, so pinging support@bitmover.com is more likely to
> > get you help.
> 
> We've exchanged some email with support@bitmover.com, and they've been
> a great help.  Really, there are two things.
> 
> The first is triggers. The Mozilla tinderbox is driven by triggers from
> CVS commits.  I believe that triggers are resevered for the commercial
> version of BK.

That's not true.  Trigger support is identical in both versions.

> However, unlike CVS, BK has a nice way of asking the remote repository
> if new changes exist, so we really don't need a trigger to tell us when
> to start a build.  

Right.  Your problem is deciding which trees you want to track.  There is 
Linus/Marcelo trees but there are probably another 200+ trees of the kernel
on bkbits.net and who knows how many elsewhere (we've counted over 10,000
before we stopped counting).  Obviously you don't want to track all of those
but some of them might be interesting.

> The main issue here is finding the proper syntax for the bkweb url so
> we get all of the changesets included in the commit. We've recieved a
> few examples from your support people, and we're using one currently.

So are there any open issues?  The call implied there were.
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm