224889 - Bitkeeper support for "bonsai" time and checkin information

Status: RESOLVED WONTFIX

(Webtools Graveyard :: Tinderbox3, defect)

Description

[Christian Reis]

In place of Bonsai, tinderbox.osdl.org needs to track Bitkeeper repositories.
The interesting part here is that Bitkeeper pretty much does what Bonsai does
for us, though the checkin notification may be the harder part to setup.

There's a syntax that can be used on bkweb to get a range of changes based on
Changeset numbers; the following returns a list of changesets from 1.1184 to 1.1192:

http://linux.bkbits.net:8080/linux-2.4/ChangeSet@1.1184..1.1192?nav=index.html

We need to find a way to specify what sort of repository backend the tree will
be relying on, I think. This is also mutually exclusive with Bonsai -- either
you're using Bonsai or you're using BKWeb, and it probably doesn't make sense to
use both on the same tree. The same server should be able to handle bonsai-based
and bk-based trees, of course.

Comment 1

[John Keiser (jkeiser)]

I think the best route to go with this is to rename tbox_bonsai_cache to
tbox_source_control_cache (or something along those lines) and tbox_bonsai to
tbox_source_control_watcher (or something, again).  This way the *display*
portion of the source control watcher tree is the same code either way.  (If the
two source control systems have sufficiently different output--and I bet they
don't--then perhaps it's worth keeping this split up.)

The admin interface is another interesting question: it can be done two major
ways.  The first is to make just one "Add Source Control Watcher" script and
have a dropdown to select which source control system.  The second is to have an
"Add Bonsai Watcher" and "Add BitKeeper Watcher" script, customized for each
system.  It all depends on just how different the configuration is for each of them.

Comment 2

[Sylvestre Ledru [:Sylvestre]]

tinderbox isn't maintained anymore. Closing!