CruiseControl.NET build error when SVN is unavailable

Question

We have an SVN repository hosted externally, and our build server is currently internal. Sometimes (probably 1 or 2 times a day), the build server cannot find the SVN repository due to a network failure, timeout, or some other random reason. With an external repository hosted, this is difficult to avoid, however, when it fails to find the SVN repository, it fails to build!

I would like to find a way to just try again at the next interval and ignore any errors related to the unreasonable repository. Does anyone know how I can do this?

I posted my configuration for the link below.

<project name="MyProject" queuePriority="0"> <workingDirectory>C:\RemovedForPost</workingDirectory> <artifactDirectory>C:\RemovedForPost </artifactDirectory> <sourcecontrol type="svn"> <trunkUrl>http://RemovedForPost \</trunkUrl> <workingDirectory>source</workingDirectory> <username>myuser</username> <password>*****</password> </sourcecontrol> <triggers> <intervalTrigger name="BuildAMinute" seconds="60" buildCondition="IfModificationExists" /> </triggers> <tasks> <msbuild> <executable>C:\Windows\Microsoft.NET\Framework\v3.5\MSBuild.exe</executable> <workingDirectory>C:\RemovedForPost</workingDirectory> <projectFile>C:\RemovedForPost\RemovedForPost.sln</projectFile> <buildArgs>/noconsolelogger /p:Configuration=Debug /v:diag</buildArgs> <targets>Build</targets> <logger>C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll</logger> <timeout>120</timeout> </msbuild> <nunit> <path>C:\Program Files\NUnit 2.5\bin\net-2.0\nunit-console.exe</path> <outputfile>C:\RemovedForPost.xml</outputfile> <assemblies> <assembly> RemovedForPost </assembly> </assemblies> <timeout>60</timeout> </nunit> </tasks> 

thanks

Answer 1

Correction. Everything you want is in the new settings.

CruiseControl.NET Docs

You can set it to not report an error until the maximum number of attempts is set. So make max at 3 and set it only to go to the publisher block (i.e. build failure) that has reached the limit. This way, 1 or 2 misses will be ok, but then 3 build failures something is wrong.