How does Trac and version control systems work together

These examples use subversion terminology

What features are supported

When looking at tickets it is useful to identify the specific revisions and modifications that were made to complete the change. This is called a TracChangeset and allowers users to clearly identify which specific modificaitons were made for a ticket.

How is it done

The integration between Trac and the version control system depends on TracLinks. Every time a change is commited to the version contro repositry a TracLinks must be used in the comment (usually refered to as a cimmit message) that includes a reference to the correct ticket

With additonal logic in the commit hooks (using subversion terminology) it is possible to reject the commit if no ticket number is supplied.

What functions are provided

• TracLinks
• TracChangeset

Example

1. A Trac link user begins work on a ticket
2. They obtain code from the version control system
3. After the work is completed they perform a commit of their modifications to the version control repository
4. The user inserts the Trac ticket number into the commit message as a TracLinks
5. Trac can now display the change set for the ticket