Add SCM System Page

This page lets you add a new SCM system to Ketura.

New SCM System

This tab enables you to define settings that will allow Ketura to communicate with your chosen SCM system. At present, Ketura is able to integrate with both Perforce and Subversion .

For further background information about Ketura’s integration with SCM systems, including how Ketura associates checked-in changes with issues and milestones, please see Integrating Ketura with Araxis Merge and SCM (Version Control) Systems.

To integrate a supported SCM system with Ketura:

Complete at least the required fields of the form.
Click the Test button to test your settings and make sure that Ketura can communicate with the SCM system.
All being well, click the Apply button.

To abandon the integration of an SCM system:

Click the Cancel button.

Description of form fields

Type	The type of the SCM system. Either Perforce or one of the several types listed for Subversion (one for each of the supported protocols).
Name	A name to identify this particular system to users (e.g. ‘Main Perforce Depot’ or ‘Central Subversion Repository’).
Username	The name of the user whose account on the SCM system Ketura will use when communicating with this SCM system.
Password	The password of the user whose account on the SCM system Ketura will use when communicating with this SCM system.
Server address	The address of the SCM Server with which you wish Ketura to communicate. For Perforce, this field should contain the fully-qualified hostname of the Perforce server and its port number. The port number should follow the hostname separated by a colon. For example: `myserver.domain.name:1666`. For Subversion, this field should be the address of the Subversion repository. The address is the URL of the repository with the protocol declaration omitted. For example: `myserver.domain.name:3690/repos/`. Care should be taken to ensure that the correct path to the repository is specified.
Executable location	The location of the executable that Ketura runs to access the SCM system. For Perforce, Ketura requires that the Perforce command line client is installed on the same computer as the Ketura server. The location of p4 on the server should be specified in this field. On Windows, the default installation location for the Perforce command line client is C:\Program Files\Perforce\P4.exe. On Mac OS X, the p4 command is commonly installed at /usr/local/bin/p4. For Subversion, Ketura requires that the Subversion svn command line client is available on the server machine. The location of the svn command should be specified in this field. On Windows, the location will be a path to the svn.exe file of the Subversion installation, for example: C:\Program Files\Subversion\svn.exe. On Mac OS X, the location will be the path to the svn binary. The Subversion command line client is usually installed so that the path to the file is /usr/local/bin/svn. Note that a version of the Subversion client is included in Mac OS X 10.5 ‘Leopard’ at /usr/bin/svn.
SCM web server	This field is shown if the selected SCM system can be accessed via a web browser. The supported types of web server can be selected from the list. If a web server has been selected and configured, the entries in the table shown on the Activity tabs of the Issue and Milestone pages may contain View links. View links enable users to access more information about a change or set of changes, by accessing the web interface of an SCM directly. View links are not shown if a web server is not configured for the SCM. A number of configuration fields might become available beneath this field when a SCM web server is selected. Directions for how to complete the fields will appear beneath the relevant fields.