Configuring source control integration
Before you can work with source control files in Helix ALM, you must enable the integration and specify your login credentials.
Note: Make sure the correct version of Helix ALM (32- or 64-bit) is installed for the source control integration to work. See the Helix ALM Integrations knowledgebase for integration requirements.
1. Choose Tools > Source Control Integration Local Options.
The Source Control Integration Local Options dialog box opens.
2. Select a Current integration option.
The list includes the Surround SCM, Helix Versioning Engine, and Subversion providers configured for the project. If your provider is available, select it and continue with step 5.
If your provider is not available, select <Custom> to manually configure the integration connection. Continue with step 3.
3. Select the provider Type. Keep the following in mind:
- Subversion versions marked as deprecated work for the specific version, but the integration libraries used will be removed in a future release. To ensure the integration uses the current libraries, select Subversion (all versions).
- CVS and Microsoft Visual SourceSafe integrations are deprecated and support will be removed in a future release. Consider using another provider.
4. Specify the provider connection information. The available fields depend on the selected provider.
| Provider | To configure a connection: |
|---|---|
| Surround SCM SCCI | Click Browse to select the server to connect to. Connect to the server and click OK. The server address and port number are displayed in the Server field. |
| Helix Versioning Engine | Enter the Server address and Port number for the Helix Versioning Engine server. |
| Subversion | Enter the Repository URL. The URL must use the correct format for the server: file:///path/to/repo for local servers, svn://hostname/repo for remote servers, http://webaddress/svn/repo for web servers (using mod_dav), and https://webaddress/svn/repo for web servers with SSL enabled. |
| CVS | Enter the Repository connection string. The string includes the authentication scheme, including username and computer if you use pserver, and CVSROOT path that are used to run the log command. It is the same connection string used in the DOS test when running the CVS log command. |
| Microsoft Visual SourceSafe | Click Browse to select the srcsafe.ini file. This file contains the path to the 'data' folder, which is where the project database is located. |
Note: If you have permission to configure source control providers, click Configure Providers to add the provider to the project so other users can select it. If you do not have permission to configure providers, ask your administrator for help.
5. Select a Source Control Application Login option.
- Use your Helix ALM username and password uses the same credentials you use to log in to Helix ALM.
- Use the following uses the specified username and password.
- Connect to Surround SCM using single sign-on uses your network credentials to connect to Surround SCM.
6. If you use Helix Versioning Engine, enter the Workspace name.
7. If you use Subversion or CVS, enter the Project working directory path or click Browse to select the directory.
8. Click Validate Connection to test the connection.
The connection results dialog box opens. If the connection fails, make sure the information is correct. Click OK to close the dialog box.
9. Click OK to save the changes.
After the integration is enabled, you can work with source files in items. See Working with source files.
