Scmbug

[Christian Robottom Reis]

On Tue, Jun 01, 2004 at 05:13:54PM +0100, Dave Swegen wrote:
> I had a look at it a while back, and the main bit that needs doing is
> cleaning up the interface (the --dont_change-- stuff is somewhat grotty,
> and I seem to recall that adding comments wasn't working). I haven't
> really had time to get the hang of what is going on in process_bug.cgi.

As I said, I think justdave's script might already handle this part.

> Also, if an error is encountered while submitting changes to multiple
> bugs the process stops as soon as the error is encountered, rather than
> printing an error and continuing. For the purposes of the cvs->bz
> script, this would be bad (mainly for performance reasons).

What sort of error?

> The horrible truth is that we can hack all sorts of stuff into bz, but
> what it really needs is a nice, consistent and defined interface that
> can deal with non-interactive external programs.

/me shrugs. I don't find the CGI interface so bad to deal with; of
course, parsing the returned data is sucky, but parsing XML is sucky
as well and the upside is that it works now.

Of course, a real interface would be much better, but we don't have one
right now (and I'm not volunteering to work on one ATM either).

> The upside of doing it is that the CVS commit would be instantaneous,
> rather than having to wait for the script to finish talking to bz (which
> as we all know can take a while). It would also cope better with bz
> being down or otherwise unavailable. 

Well, you say below you're using an email interface, so the CVS commit
would have to wait, at the most, for email to be dispatched, right?

> > What about some bz->bonsai autolinking while we're at that? :-)
> 
> Shouldn't be too hard. Surely it should just be a case of coming up with
> what links you want for files and versions and changing the URLs we use
> to something else. Then again, I know very little about bonsai, apart
> from that it makes bz look pretty by comparison.

To be honest, the links should probably have the same syntax and just
point to different servers depending on which system you have installed.
A simple param could configure if we've got bonsai, viewcvs or cvsweb,
for instance.

> The delivery method from cvs to the script that bungs things into bz: We
> use email, and this new method uses a custom server. 

How does the CVS loginfo script talk to the custom server?

Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331