It’s not at all at a point where it’s stable, well documented, robust,
etc, but I now have my RT instance recording ticket updates from svn
commits that identify tickets.
In the coming days and weeks, I’ll be polishing this up and releasing
it, but it seems to let me record comments and resolve tickets on
subversion commits, which, along with RT 3.1’s slightly cleaned up CLI
means that I can now apply patches in seconds instead of minutes. Which
is always a happy thing 
In your svn post-commit hooks, add the following:
curl “http://your RT
server/SVN/Look.html?user=guest&pass=guest&rev=$REV”
Curl isn’t a requirement. you just need something that can “ping” your
RT server via http.
the guest account isn’t a requirement. it just needs to be a privileged
account that can get at RT’s UI.
The svn handler on the RT side makes sure you don’t repeatedly apply
commits using links from tickets to the relevant svn transactions.
Install the attached “Look.html” file as
/opt/rt3/local/html/SVN/Look.html
Look.html (1.79 KB)
PGP.sig (186 Bytes)
Evan as a user of both Subversion and RT, I don’t really
have a clue what you’re talking about. What capability does this add to RT,
and which RT version is required to give it a spin?
Thanks,
POn Fri, Mar 12, 2004 at 12:59:12AM -0500, Jesse Vincent wrote:
It’s not at all at a point where it’s stable, well documented, robust,
etc, but I now have my RT instance recording ticket updates from svn
commits that identify tickets.
In the coming days and weeks, I’ll be polishing this up and releasing
it, but it seems to let me record comments and resolve tickets on
subversion commits, which, along with RT 3.1’s slightly cleaned up CLI
means that I can now apply patches in seconds instead of minutes. Which
is always a happy thing
In your svn post-commit hooks, add the following:
curl “http://your RT
server/SVN/Look.html?user=guest&pass=guest&rev=$REV”
Curl isn’t a requirement. you just need something that can “ping” your
RT server via http.
the guest account isn’t a requirement. it just needs to be a privileged
account that can get at RT’s UI.
The svn handler on the RT side makes sure you don’t repeatedly apply
commits using links from tickets to the relevant svn transactions.
Install the attached “Look.html” file as
/opt/rt3/local/html/SVN/Look.html
rt-devel mailing list
rt-devel@lists.bestpractical.com
The rt-devel Archives
Peter Burkholder, System Administrator
Digital Library for Earth System Education (DLESE® – http://www.dlese.org)
Email) peterb@ucar.edu ~~~ ~~ ~~~ __o
DLESE Program Center (DPC) Office) +1-303-497-2663 ~~~ ~~~ ~~ `<,
UCAR/DPC, P.O. Box 3000 Fax) +1 303-497-8336 ~~~ ~~~ ~~~~ ()/ ()
Boulder, CO 80307-3000 Pager) +1-303-201-1284 or peterb-page@dpc.ucar.edu
Evan as a user of both Subversion and RT, I don’t really
have a clue what you’re talking about. What capability does this add
to RT,
and which RT version is required to give it a spin?
if your commit log looks like this:
RT-Ticket: 23
RT-Status: resolved
this is a commit log
then RT will add the commit log to ticket 23, resolve ticket 23 and
make ticket 23 “link” to the transaction.
Linking to the transaction doesn’t currently do much, but in the
future, it should like to viewcvs or some other similar tool
PGP.sig (186 Bytes)
if your commit log looks like this:
This is awesome. Thank you again, Jesse. One more item to cross off my
“I really should try to do this…” list. Now to rebuild my dev server
so I can try it out. 
Michael
Michael S. Liebman m-liebman@northwestern.edu
http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”