If your source control system is not on this list of articles on this Source Control Integration page, you can still integrate it with Manuscript. There are two aspects to source control integration:

  1. Getting your source control system to transmit changes to Manuscript
  2. Getting Manuscript to provide links to a URL that shows diffs and history logs from your source control system

Getting your source control system to transmit changes to Manuscript

You need to install a “trigger” script in your source control system to notify Manuscript whenever a check-in occurs that is related to a particular bug. You will have to implement this script yourself to integrate with whatever hooks, triggers, or APIs your source control system offers.

The way these scripts work is they send the check-in information via HTTP to a Manuscript ASP page named cvsSubmit.asp, using a URL like:

http://your.manuscript.server/cvsSubmit.asp?ixBug=bugID&sFile=file&sPrev=x&sNew=y&ixRepository=RepositoryID

Where:

  • bugID is the Manuscript case number
  • file is the source file that is being checked in
  • x is the previous revision number
  • y is the new revision number
  • RepositoryID is the ID of the repository you create in Manuscript. You can get this value from the New Repository dialog (see below).

Getting Manuscript to Provide Hyperlinks to Your Source Control Viewer

Log into Manuscript as an administrator and go to the  Avatar menu > Source Control. Click Create New Repository. In the resulting dialog, select Other (custom) as the type and give the repository a display name. Click Next.

Under Diff URL, enter the URL of your source control system diff viewer.

In this URL, ^FILE will be replaced with the file name, ^R1 will be replaced with the old version number, and ^R2 will be replaced with the new version number.

Under Log URL, enter the URL of your source control system history viewer.

In this URL, ^FILE will be replaced with a file name for which Manuscript wants to display the history.