mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: cliff white <cliffw@osdl.org>
To: Larry McVoy <lm@bitmover.com>
Cc: hannal@us.ibm.com, lse-tech@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] Re: Minutes from OSDL talk at LSE call today
Date: Thu, 4 Dec 2003 13:45:17 -0800	[thread overview]
Message-ID: <20031204134517.0c7a4ec4.cliffw@osdl.org> (raw)
In-Reply-To: <20031204033535.GA2370@work.bitmover.com>

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.

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. 
Instead, we run the timestamp column on a cron, so it is constantly incrementing.
( Mozilla only increments their timestamp column when a trigger is recieved ) 

The change from trigger-driven to time-driven timestamps meant we didn't try 
to create a link between timestamp->source commit. Again, since Mozilla is
trigger driven, they have this link.

So, the second piece is linking either the time-stamp column or the build machine column
directly to a Web-based view of the code. BkWeb already provides the view. 

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. 

cliffw


> -- 
> ---
> Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by OSDN's Audience Survey.
> Help shape OSDN's sites and tell us what you think. Take this
> five minute survey and you could win a $250 Gift Certificate.
> http://www.wrgsurveys.com/2003/osdntech03.php?site=8
> _______________________________________________
> Lse-tech mailing list
> Lse-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lse-tech
> 


-- 
The church is near, but the road is icy.
The bar is far, but i will walk carefully. - Russian proverb

  reply	other threads:[~2003-12-04 21:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04  1:20 Hanna Linder
2003-12-04  3:35 ` Larry McVoy
2003-12-04 21:45   ` cliff white [this message]
2003-12-04 22:54     ` [Lse-tech] " Chris Wright
2003-12-04 23:44     ` Larry McVoy
2003-12-09 18:53       ` cliff white
2003-12-09 21:26       ` Zwane Mwaikambo
2003-12-09 21:48         ` Larry McVoy
2003-12-09 21:54           ` Zwane Mwaikambo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031204134517.0c7a4ec4.cliffw@osdl.org \
    --to=cliffw@osdl.org \
    --cc=hannal@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=lse-tech@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®