This article provides details on how to configure the SubVersion Integration in Manuscript.
All Agents, End-User
- Navigate to Avatar Menu and click Source Control.
- Choose “Create New Repository” and select “Subversion”.
- Give your repository reference a Name, then click Next.
Note: The resulting dialog contains scripts and instructions for getting Subversion to transmit changes to Manuscript. Those instructions are provided in more detail below. Select the appropriate tab for the server Subversion runs on and download the scripts. Before you close the dialog, choose whether you want Manuscript to provide links to your check-ins. You can change this setting later by clicking the Edit icon next to the repository on the Avatar Menu > Source Control page.
Diff and log links
In order to have Manuscript link to checked-in files directly from cases, you need something that allows you to view file diffs and history logs from a web browser. We recommend WebSVN. You can also setup Manuscript to link to logs and diffs in Trac. Once you have WebSVN or Trac installed and working with your Subversion repository, set the path to it in the New Repository dialog and click OK to complete the setup.
Getting Subversion to transmit changes to Manuscript
If your Subversion server is Linux or Unix, make sure that Perl is installed. If your Subversion server is Windows, make sure it has Windows Scripting version 5.6 or later installed.
Put the logBugDataSVN and post-commit scripts you downloaded above into Hooks directory in your Subversion repository. If your SVN repository is on Unix, grant executes permissions on both files (chmod +x filename). If you already have a post-commit script, you will need to merge it with this one.