Subversion Source Control Block¶

CruiseControl.NET provides basic support for Subversion repositories. Checking for changes, checking out or updating sources, and tagging-by-copying are supported, but more advanced features such as using Subversion revision numbers are not yet supported. Subversion support is under active development and will improve over time.

Version¶

Available from version 1.0

Examples¶

1<sourcecontrol type="svn">
2  <trunkUrl>svn://svn.mycompany.com/myfirstproject/trunk</trunkUrl>
3  <workingDirectory>c:\dev\ccnet</workingDirectory>
4</sourcecontrol>

Configuration Elements¶

* None
* ExternalsOnly
* Always

Notes¶

The <trunkUrl> tag should specify the URL to use to determine if changes have occurred in your repository.

You need to make sure your SVN client settings are such that all authentication is automated. Typically you can do this by using anonymous access or appropriate SSH setups if using SVN over SSH.

Linking modifications to WebSVN¶

You can link the modifications detected by CruiseControl.NET to the appropriate WebSVN page by adding the following additional configuration information to the Subversion source control section:

1<webUrlBuilder type="websvn">
2  <url>http://localhost:7899/websvn/diff.php?repname=MiniACE&amp;path={0}&amp;rev={1}&amp;sc=1</url>
3</webUrlBuilder>

Change the <url> element to point to the root url for the WebSVN site. The path and rev parameters will be filled in by CruiseControl.NET when it generates the link to the code file page.

The standard url for WebSVN 1.38 contains rep=3 r instead of repname=MiniACE. Adding a new repository to the SvnParentPath will change the number of the rep parameter, so you may need to make the following change to diff.php to decode the repname parameter:

1            $repname = @$_REQUEST["repname"];
2
3            if (isset($repname))
4            {
5            $rep = $config->findRepository($repname);
6            }
7            

The WebSVN WebUrlBuilder can also be used to connect to a ViewCV site. Here is an example used by CCNet to link to the file revision pages on SourceForge:

1<webUrlBuilder type="websvn">
2  <url>http://svn.sourceforge.net/viewvc/ccnet/{0}?view=markup&amp;pathrev={1}</url>
3</webUrlBuilder>

SVN over SSL¶

When connecting to a Subversion repository via SSL (https), you may be required to accept an issued server certificate. This generally requires responding to a command-line prompt that the certificate should be accepted permanently. For CruiseControl.NET, all Subversion commands are executed using the --non-interactive switch, which will cause this prompt to be skipped and the subsequent Subversion command to fail with a message like this:

1            svn: PROPFIND request failed on '/svnroot/ccnet'
2            svn: PROPFIND of '/svnroot/ccnet': Server certificate verification failed: issuer is not trusted (https://ccnet.svn.sourceforge.net)
3            

As the failure will happen on the first Subversion command to be executed, this failure will not show up as a broken build, but will instead show up in the server log.

One way to resolve this problem is to execute a command against the Subversion repository from the command-line logged in as the user that you are using to run CCNet (certificates are cached by user account, so you must accept the certificate for the appropriate user). For example, try executing the following command (where trunk_url is the svn url for your repository):

1            svn list [trunk_url]
2            

When prompted to accept the certificate, type 'P' to permanently accept it.

If you are running CCService under the LocalSystem account, you will need to accept the certificate for this user. Check out the CCService page for information about how to diagnose problems as the LocalSystem account.

External contributors: Matt Petteys

SVN over svn\+ssh¶

To connect to Subversion with the svn\+ssh protocol, here is an excerpt from the article HowTo: Configure SVN\+SSH with Subclipse on Windows by Martin Woodward. For more details, see the complete article (http://www.woodwardweb.com/archive/200511.html).

HowTo: Configure SVN\+SSH with Subclipse on Windows

You need to create an environment variable called "SVN_SSH" that points to an executable file that accepts the same command line arguments as ssh on unix. I did this by doing the following:-

1: Set up ssh keys. Not going to cover that here as you can easily Google for that. You need to end up with your public key on the SVN server and your private key loaded into Paegent locally.

2: Download and installed the excellent TortoiseSVN client for Windows.

3: Set the following environment variable (by right-clicking on My Computer, Properties, Advanced, Environment Variables, New):-

1            Variable name: SVN_SSH
2            Variable value: C:\\Program Files\\TortoiseSVN\\bin\\TortoisePlink.exe
3            

The "\ \"(double-back-slash) is very important, otherwise it won't work. Equally, you cannot use the plink.exe that comes with putty as that fires up a command shell window which is really annoying. The TortoisePlink.exe is a windows implementation of plink that doesn't bring up any UI.

Known Issues¶

CruiseControl.NET doesn't see my changes

The Subversion interface depends on the clocks of the CruiseControl.Net and Subversion servers being set within a small difference. Due to a long-standing Subversion bug (Bugzilla #1642) that appears unlikely to ever be fixed, CruiseControl.Net must filter the list of modifications returned by Subversion, looking for only those that fall within a specific time range. When the clocks of the two servers are significantly different, the filter may ignore modifications that should not be ignored. To prevent this problem, keep the clocks of the two servers set as closely together as possible.

Dashboard Localization (issues with SVN)¶

I've found that svn has a trouble with --xml parameter. My russian Log Messages were not readable.

I found a quick solution for it, next items could be customized to any languges. But be sure this is not the panacea. So in all .xsl files where comments or filename in Russian local I've added following "translation"

            <xsl:value-of select="translate(comment,'??????????????????????????????????????????????????????????????????',
            '????????????????????????????????????????????????????????????????')"/>
            

Where comment from /cruisecontrol/modifications/modification, and "??" in second parameter are symbols to delete, all others are mathed with third parameters. As I found xsl could only translate char strings , if some one know the way to translate double-char symbols, please note about it. In this way you can help your self for modification for any charset.

I agree with everyone that it is a rude solution. But for my no time to wait untill svn or cc.net will be customized for that feature.

Automatically Generated¶

Documentation generated on Monday, 26 May 2014 at 7:18:02 AM