Edgewall Software

Changes between Version 314 and Version 315 of 0.12/TracFaq


Ignore:
Timestamp:
Jun 15, 2010, 10:32:54 AM (14 years ago)
Author:
Mikael Relbe
Comment:

Updated description on ticket updates when committing changesets (ticket:9120#comment:8)

Legend:

Unmodified
Added
Removed
Modified
  • 0.12/TracFaq

    v314 v315  
    608608=== Can Trac automatically update a ticket when I commit a changeset? === #can-trac-automatically-update-a-ticket-when-i-commit-a-changeset
    609609
    610 Yes, you can setup Subversion to update the Trac ticket when you commit changes with a message listing tickets that are fixed or related.  You can read the comments in the beginning of the file contrib/trac-post-commit-hook  source:/trunk/contrib/trac-post-commit-hook for more information on how to set this up.
    611 
    612 If you are using a stable version rather than the latest development version you should instead get the script which matches your release - for example source:/branches/0.9-stable/contrib/trac-post-commit-hook ('''if you build from source, you will find the correct script version in your trac-xxx/contrib folder''')
     610Yes, you can setup Subversion to update the Trac ticket when you commit changes with a message listing tickets that are fixed or related.
     611
     612==== Trac 0.12
     613Trac 0.12 introduced a new, more general, method to accomplish this. You can, for example, activate the optional !CommitTicketUpdater plugin that is part of Trac 0.12, and then define repository hook scripts as described [TracRepositoryAdmin#ExplicitSync here].
     614
     615For more info about the optional !CommitTicketUpdater plugin provided by Trac, see the file tracopt/ticket/commit_updater.py source:/trunk/tracopt/ticket/commit_updater.py.
     616
     617For another example on how to relate tickets and changesets, see TracHacks:TracTicketChangesetsPlugin.
     618
     619==== Trac 0.11 and previous versions
     620
     621If you are using a stable version prior to Trac 0.12, you should instead get the script which matches your release - for example source:/branches/0.11-stable/contrib/trac-post-commit-hook ('''if you build from source, you will find the correct script version in your trac-xxx/contrib folder''')
    613622
    614623If the trac-post-commit-hook script does not appear to be working, for some extra clues try running it from the command-line using the account normally used to run it and without an environment (as it's normally executed).