| | 1 | = How does Trac and version control systems work together = |
| | 2 | |
| | 3 | ''These examples use subversion terminology'' |
| | 4 | |
| | 5 | == What features are supported == |
| | 6 | |
| | 7 | 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. |
| | 8 | |
| | 9 | == How is it done == |
| | 10 | |
| | 11 | 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 |
| | 12 | |
| | 13 | With additonal logic in the commit hooks (using subversion terminology) it is possible to reject the commit if no ticket number is supplied. |
| | 14 | |
| | 15 | == What functions are provided == |
| | 16 | |
| | 17 | * TracLinks |
| | 18 | * TracChangesets |
| | 19 | |
| | 20 | |
| | 21 | == Example == |
| | 22 | |
| | 23 | 1. A Trac link user begins work on a ticket |
| | 24 | 1. They obtain code from the version control system |
| | 25 | 1. After the work is completed they perform a commit of their modifications to the version control repository |
| | 26 | 1. The user inserts the Trac ticket number into the commit message as a TracLinks |
| | 27 | 1. Trac can now display the change set for the ticket |
