[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Trac/bugtraq - Ticket to Changeset link [was: Re: Trac [was: TortoiseSVN 1.1.1 released]]

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-10-27 16:33:34 CEST

Mark Phippard <MarkP@softlanding.com> wrote on 10/27/2004 10:10:17 AM:

> > - Instead of a script, how about an URL pointing to a file which a
> > client can download, parse and get the open issues from that file.
> > Trac (or any other Bugtracking system) could generate that file on
> > request like a dynamic webpage. Problem here: what if that list is
> > 'protected', i.e. if you have to authenticate to just get that file?
> I do not want to over-engineer this, but when I was thinking about this,
> felt that this is the perfect candidate for a Web Services approach.
> is more or less the same as what you are suggesting, there just may be
> some standard approaches we could follow like using SOAP or XML-RPC.

I was re-reading some notes I had written down in the past, and here is
another idea I had.

Implement this feature using something like client-side hooks. Perhaps,
to configure this, you set a property that defines a command-line option
to execute, this would allow custom parms to be passed to the program by
setting those parms in the property. Perhaps TSVN would always pass a
filename as the first parm, and it would be up to the program to populate
that file?

Anyway, to meet some of your other requirements, TSVN could simply come
with a program that provides a default implementation. In other words, a
program that hits a URL and populates the file. This would provide an out
of the box solution for most situations, but still provide flexibility.
Not all bug tracking tools use HTTP, and this would allow those tools to
still integrate with this feature.

As an example, the property someone might set when using the default
program might look like this:

bugtraq:listprovider = TortoiseBugTraq.exe %BUG_LIST%

%BUG_LIST% would be a temp file that TSVN asks the program to write the
results to. You could probably define a custom-formatted file, presumably
XML, that the provider would have to create. When hitting the URL, it
would be expected that the contents of that file would just be returned to
your program to write.

I think this would provide a lot of flexiblity, while still allowing TSVN
to provide an out of the box robust implementation.

A similar approach could be used to define a pre-commit validation


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 17:37:44 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.