Search:     Advanced search

Surround SCM Hudson and Jenkins Integration

Article ID: 761  |  Last updated: 18 Nov, 2016

Surround SCM supports integration with Jenkins. See Surround SCM Third-Party Integrations for supported platforms and versions.

This article includes information about the integration requirements, installing the plug-in, configuring a job to use Surround SCM, and synchronizing workspaces with Surround SCM.

Note: The following information also applies to Hudson integration, but it is not officially tested or supported by Seapine.


  • The Surround SCM command line client (CLI), sscm.exe, must be installed on the computer running Hudson or Jenkins. 
  • You must have permission to log in to the Surround SCM CLI and to view and get files. 
  • Your Surround SCM user options, such as text file format, must match the development settings for the Hudson or Jenkins project.

Installing the plug-in

Download the plug-in and save it in the plugins subdirectory in the Hudson or Jenkins directory. For example, C:\hudson\plugins (Windows) or $JENKINS_HOME/plugins (Unix). After the plug-in is installed, restart the tool.

Configuring a job to use Surround SCM

  1. In Hudson or Jenkins, create a new project.
  2. Select Surround SCM in the Source Code Management options. The Surround SCM connection information fields are displayed.
  3. Enter the path to the Surround SCM CLI. For example, C:\Program Files\Seapine\Surround SCM\sscm.exe.
  4. Enter the Surround SCM Server name, Server port, Username, and Password. 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 of the server address and port.
  5. Enter the Branch name and Repository path to poll from or synchronize with your workspace.
  6. Set any additional options for build triggers or steps.
  7. Save the configuration. The job option is added to the main Hudson or Jenkins page.

Synchronizing workspaces with Surround SCM

The plug-in supports polling, synchronizing, and browsing latest changes. If polling is enabled, Hudson or Jenkins polls the Surround SCM repository to check for changes. If changes are found, the workspace is synchronized with the repository and a build is automatically started. All files are retrieved to the workspace subdirectory in the Hudson or Jenkins job directory. You cannot change the directory to retrieve files to.

If a build is manually started, a get command is performed to synchronize the workspace with the repository. Gets performed on the repository and branch specified in the job configuration are recursive.

After a build, you can use the Changes and Console Output options to view the changes and output.

Article ID: 761  |   Last updated: 18 Nov, 2016
Hudson Jenkins

Prev   Next
Surround SCM Xcode 4 Integration     Surround SCM Dreamweaver Integration