Surround SCM Plugin

Skip to end of metadata
Go to start of metadata

This plugin integrates with Seapine Software's Surround SCM.

Plugin Information

Plugin ID Surround-SCM-plugin Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.2
Aug 12, 2013
1.377
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Paul Vincent (id: n/a)
Usage Installations 2013-Apr 44
2013-May 58
2013-Jun 58
2013-Jul 62
2013-Aug 63
2013-Sep 57
2013-Oct 63
2013-Nov 72
2013-Dec 63
2014-Jan 65
2014-Feb 75
2014-Mar 82

Requirements

  • The Surround SCM command line client (CLI), sscm.exe, must be installed on the computer running 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 Jenkins project.

Installing the plug-in

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

Configuring a job to use Surround SCM

1.       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.

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 Jenkins page.

Synchronizing workspaces with Surround SCM

The plug-in supports polling, synchronizing, and browsing latest changes. If polling is enabled, 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 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. All get commands through Jenkins to the repository on the branch specified in the Surround SCM job configuration are recursive.

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

Troubleshooting

Please contact Seapine support with questions about the integration or to report bugs or feature requests.

Labels

Edit
plugin-scm plugin-scm Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.