Subversion Integration

This section describes CodeCollaborator integration with Subversion:

The CodeCollaborator server can pull committed revisions directly from your Subversion server for review, without users needing to install any client programs.

The GUI Client can upload local changes to files in a Working Copy, or upload the files in Revisions. The GUI Client can also upload arbitrary Subversion diffs, or the difference between two Revisions, branches / tags, or dates.

The Command Line Client can upload local changes to files in a Working Copy, or upload the files in committed Revisions. The Command Line Client can also upload arbitrary Subversion diffs.

Eclipse Plug-in

The Eclipse Plug-in integrates with the Subclipse and Subversive plug-ins so you can upload locally modified files or upload the files in Revisions.

Subversion server-side hooks can ensure code is reviewed or automatically create reviews.

Our Command Line Client and GUI Client integrations use your own Subversion command-line client (svn) to communicate with the server. We support these versions:

Our Eclipse Plug-in integrates with the Subclipse and Subversive Eclipse plug-ins. We support these versions:

Because we use Subversion client applications already present on your computer, we support all protocols, authentications, proxies, and other client configuration options you are currently using.

CodeCollaborator partially supports Subversion's concept of directories (not just files) being altered.

All files underneath the directories in question will be scanned, uploaded and represented properly in the GUI. The directories themselves will not be shown in any GUI, or even in the file list confirmation screen presented by the command-line client.

This all works correctly even if for example you move a parent directory and alter/add/delete a file within that directory. You'll get the correct content for the file but the directory itself will not be listed in the review.

Note this limitation affects "commit" functionality. If a directory is and a file within it are modified and reviewed, the CodeCollaborator client will not be able to commit them automatically. The workaround is to commit the changes manually and then "dismiss" the commit Action Item.

The CodeCollaborator clients support running Subversion over SSH (the svn+ssh:// protocol). On some systems, especially those under Unix, Mac OS X or Cygwin/Windows, this will probably work correctly out of the box.

If a banner is displayed by your SSH connection, this will interfere with the client being able to correctly parse Subversion output. You should be able to suppress SSH banner output by adding the "-q" option to your SSH executable, i.e.:

svn_ssh = ssh -q

or by creating a local SSH configuration file and adding the line:

LogLevel QUIET

For some Windows installations, especially with TortoiseSVN, you might have to configure Subversion to default to your SSH client. To do this, go to APPDATA\Subversion and edit the config file (here APPDATA refers to your Profile directory under Application Data, so e.g. C:\Documents and Settings\username\Application Data). Find the line under the [tunnels] section that starts with "ssh=". Set this to use your SSH client, which if you use TortoiseSVN will look something like:

ssh = "C:\\Program Files\\TortoiseSVN\\bin\\TortoisePlink.exe" -l <your username>

Note that those double-slashes are important!

CodeCollaborator doesn't specifically support reviews of the changes to Subversion properties.

CodeCollaborator partially supports Subversion's ability to version Symlinks. A Symlink contained in a committed Revision uploaded to a Review will be displayed correctly. However a Symlink uploaded to a Review before commit will have incorrect content (the Symlink will be traversed).