The SVN manual has the goods about pre-commit and post-commit.
Note that bugtraq:message is recognized by tortoise and causes TSVN to
add the Bug-Id / Issue-Nr: field in the top right hand corner of the
commit window. Then, the number placed here gets carried through into
the log message. It is simply some "lipstick" which allows data to be
tunneled through the log message. The "lipstick" is the field on the
window. AFAIK, there isn't a way to get the tortoise shell to show your
own fields in a declarative way. You would have to crack the code.
But, you can "add" whatever hidden data you want to the log message and
use a RegEx in your hook to pull it out. You could do something like:
YourHours: 5 and look for this with a RegEx.
For example, we support merge transactions in our SCM system built on
top of SVN. This prevents someone from merging the same file twice from
a branch to trunk when porting patches. It also makes sure all changes
get ported because we can query for files that didn't make it. Anyways,
our infrastructure starts a merge transaction, gets the list of all the
files, does the svn merge and commits the files to trunk. To do this,
we tunnel info into the log message to keep track of the state. We grab
this data in the hook scripts and commit it to our SCM database.
-----Original Message-----
From: Jonathan L. [mailto:jleibiusky@quadratica.com.ar]
Sent: Tuesday, February 07, 2006 9:36 AM
To: users@tortoisesvn.tigris.org
Subject: Re: TSVN & Bug Tracking Integration
That's nice. Can you tell me where can i find more info about pre-commit
and post-commit hooks?
What if i want to associate with the commit not only the bugid but also
the amout of hours it takes me to resolve that bug? A lot if issue
trackers have this feature but it seems it cannot be integrated with
svn, am i wrong?
Jonathan
Scott Prugh wrote:
> We just converted from Sourcesafe and had a custom integration to our
> tracking systems.
>
> On SVN, we created hook scripts on the backend and enabled the
> bugtraq:message property on the repository.
>
> On the pre-commit we confirm that a bugid comes through on each commit
> and also make sure that the bugid matches the branch the code is being
> checked into.
>
> On the post-commit, we log all the information and tie the file
checkin
> to the bugid. Our packaging system then uses all this to determine
> which incidents are ready and which files to deliver with each
incident.
>
> It works like a charm.
>
> At first, I was concerned that the overhead of spawning a process with
> each pre-commit and post-commit would be really slow and that I would
be
> forced to do more of a native integration with the lower level APIs.
> But, we have seen that the performance is very good and we have not
> needed to do that.
>
>
> You mention forking a process, but the hook mechanism is already doing
> that. Note that the pre-commit must occur synchronously so you will
> not get any benefit there by spawning a second process.
>
> If spawning your hooks are too slow, perhaps your machine is under
> powered(cpu, memory).
>
>
> -Scott
>
> -----Original Message-----
> From: Jared Armstrong [mailto:jarmstrong@omnispear.com]
> Sent: Tuesday, February 07, 2006 9:00 AM
> To: users@tortoisesvn.tigris.org
> Subject: RE: TSVN & Bug Tracking Integration
>
>
> What are your commit times like with your issue tracking integration?
> Mine was so slow I had to remove it until I can get a new method setup
> that forks off the process from the commit action.
>
> Thanks,
>
> Jared Armstrong
>
>
> -----Original Message-----
> From: Peter Mounce [mailto:Peter.Mounce@whitbybird.com]
> Sent: Tuesday, February 07, 2006 4:10 AM
> To: users@tortoisesvn.tigris.org
> Subject: RE: TSVN & Bug Tracking Integration
>
>
>> -----Original Message-----
>> From: Jonathan Leibiusky [mailto:jleibiusky@quadratica.com.ar]
>> Sent: 06 February 2006 19:39
>> To: users@tortoisesvn.tigris.org
>> Subject: TSVN & Bug Tracking Integration
>>
>
>
>> Can any body share is experiences with Bug Tracking Integration?
>>
>
> Well, it works really well. What are you after, specifically? :)
>
> Pete
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Feb 7 21:15:23 2006