Surround SCM supports integration with TeamCity. See Surround SCM Third-Party Integrations for information about supported platforms and versions.
This article includes information about integration requirements, installing the plug-in, configuring a Surround SCM repository as a VCS root, and managing the version control username setting for notifications.
- The Surround SCM command line client (CLI), sscm.exe, must be installed on the build server computer. If you use agent-side check outs, the CLI must also be installed on the agent computer.
- You must have permission to log in to Surround SCM and get files. If you use labels in TeamCity, you must use Surround SCM 2013.2 and later and have permission to label files in Surround SCM.
Installing the plug-in
Note: If you upgrade Surround SCM, you should also upgrade the TeamCity integration plug-in. The plug-in is backward compatible. It supports data created using earlier plug-in versions, but not later versions.
- Stop the TeamCity server.
- Download the plug-in and save it the plugins subdirectory in the TeamCity data directory (e.g., C:\ProgramData\JetBrains\TeamCity\plugins on Windows or $HOME/.BuildServer/plugins on Unix).
- Start the TeamCity server. The plug-in files are automatically unpacked.
Configuring a Surround SCM repository as a VCS root
The Version Control System (VCS) root is the Surround SCM branch and repository to associate with your build configuration.
- In TeamCity, choose Administration > Edit Build Configuration > Edit VCS Root.
- Select Surround SCM as the Type of VCS and enter a unique VCS root name.
- Enter the Surround SCM Application Directory path. The path must end with a slash. For example, C:Program FilesSeapineSurround SCM (Windows) or /usr/bin/ (Unix).
- Enter the Full Path to Repository you want to use as the root and the Branch name. The repository path cannot end with a slash.
- Enter the Surround SCM Server Address and Server Port. If you received a server settings file for RSA key exchange from your Surround SCM administrator, enter the full path to the XML file instead.
- Select Username and Password as the Authentication Method and enter the Surround SCM username and password.
- Specify the Checking interval to indicate how often TeamCity should check Surround SCM for changes.
- Optionally select Make this VCS root available for all projects.
- Click Save to attach the VCS root to the build configuration.
Managing version control username settings for notifications
To receive notifications about changes included in builds, you must update the VCS username association setting to use the following format: LastName, FirstName Initial. Do not use your Surround SCM username. See the TeamCity documentation for information about managing your user account.