Rob Wilkerson kirjoitti: > I'm not sure whether I'll be able to help, but I'm also not sure I > understand your question. What, exactly, are you trying to do? Are > you trying to create a post-commit hook to mark tickets fixed, closed, > etc.? Or something else? > > On 10/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Hi Folks, >> >> Trying to get the BugTracker (trac) setup with TSVN. I am trying to get it >> very simply set up to see the methodology but am not sure on the syntax or >> the steps and order of those steps. Anyone have a crib available that >> describes ? Would appreciate very much any info. Thanks!
(I'm not big fan of topposting, makes hard to read and specially reply) Basically it is all about this. 5.24. Integration with Bugtracking Systems / Issue trackers It is very common in Software Development for changes to be related to a specific bug or issue ID. Users of bug tracking systems (issue trackers) would like to associate the changes they make in Subversion with a specific ID in their issue tracker. Most issue trackers therefore provide a pre-commit hook script which parses the log message to find the bug ID with which the commit is associated. This is somewhat error prone since it relies on the user to write the log message properly so that the pre-commit hook script can parse it correctly. TortoiseSVN can help the user in two ways: 1. When the user enters a log message, a well defined line including the issue number associated with the commit can be added automatically. This reduces the risk that the user enters the issue number in a way the bug tracking tools can't parse correctly. Or TortoiseSVN can highlight the part of the entered log message which is recognized by the issue tracker. That way the user knows that the log message can be parsed correctly. 2. When the user browses the log messages, TortoiseSVN creates a link out of each bug ID in the log message which fires up the browser to the issue mentioned. ... So, first one is just to matter have correct regular expressions and probably post commit hook that can automatically mark bug solved. Second one is a bit more trickier. I would be happy if someone can provide samples to do that. -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~----------~----~----~----~------~----~------~--~---
