Mingle can easily integrate with your team's subversion repository to link your code to bugs and requirements. By typing card numbers in the subversion commit messages, Mingle automatically links code revisions with the cards that are referenced. All code revisions are also linked to Mingle's History tab, so you can always see what code changes happened relative to other changes in the project.
Note: Your subversion repository must be on the local file system (relative to Mingle's installation). This is because Mingle's SVN integration feature is read-only. For remote SVN repositories, you can set up an NFS mount, or setup an 'rsync' script to keep an up-to-date copy of the repository on the local file system.
Mingle's Source tab lets you browse your entire SVN directory and shows:
Hint: Mingle's SVN integration is a great way to help new team members easily discover the code used to implement business features.
Mingle automatically scans all files in your SVN repository (based on the local directory path specified under Project admin > Project settings), and displays all revisions on the History tab.
From the Source tab you can click on a revision number to view the source files that were changed in the revision and the actual changes against the previous version (diffs).
Hint: You can view all source revisions on the History tab. If you enter a card number in a commit message (using the correct card keywords) the messages in Mingle will contain links to those cards. Viewing a linked card's history displays the source revision number (which you can then click to view other changes for the revision).
Back to Customizing projects