Search: Advanced search
Please enter a keyword or ID
Surround SCM CruiseControl.NET Integration
Surround SCM supports integration with CruiseControl.NET. See Surround SCM Third-Party Integrations for supported versions.
Note: The following example was tested using CruiseControl.NET 1.6.7981.1 and Surround SCM 2012.1.
The login credentials used to connect to the Surround SCM Server are displayed in build reports and any batch files used to create snapshot branches or labels. The build user must have read-only access at the file level and permission to log in from the Surround SCM CLI, get files, and create branches.
To use the integration, add the project files to Surround SCM and the following information to the CruiseControl.NET server configuration file (e.g., C:Program FilesCruiseControl.NETserverccnet.config).
The attached file is an example configuration file for a C# application named WysiCM.
Note: The Surround SCM CLI requires quotation marks around parameters that contain spaces. For example,
Branching and labeling variables cannot be used in the configuration file. If you want to create a snapshot branch or label after the build is complete, you can create a batch file to execute the commands.
For example, the snap.bat file used to create a snapshot in the example contains the following:
sscm mb "WysiCM 1.x - %CCNetBuildDate%" "WysiCorp Products/WysiCM" -b"WysiCM 1.x" -cc"CC.NET Build" -ssnapshot -yAdministrator: -z127.0.0.1:4900
To start a build, double-click the CruiseControl.NET server executable (e.g., C:Program FilesCruiseControl.NETserverccnet.exe). The CruiseControl.NET command console opens and displays the build progress. Close the console when the build finishes. If the console remains open, CruiseControl.NET rebuilds the application every time it detects a change in the source files.
Use the ccnet.log file (e.g., C:/Program Files/CruiseControl.NET/server/ccnet.log) to troubleshoot failed builds.