Hi Like the documentation said, it is only in getmodifications.
so should the server go down between 'getmodifications' and let's lay label, the build will still fail. But these are very small timeframes, and very unlikely to occur, but it is possible. if you do the getting of the source via a nant script, and not via a sourcecontrol block in ccnet those settings will indeed not help. with kind regards Ruben Willems On Thu, Apr 23, 2009 at 9:11 AM, Daniël <[email protected]> wrote: > > Hi Ruben, > > The sourceControlErrorHandling options seems to do the trick. I am > only worried about the "(during GetModifications)" part in the > documentation for it. That does catch all operations in CruiseControl, > or can for instance an update still fail if SVN fails? > > Besides that, we also use SVN in our NAnt scripts, which may fail > also. > > I have tested it on 1.4.4 RC1, and so far for the GetMOdification this > absolutely solves (or should I say works around) the issue in SVN. > > With regards, > > Daniël > > > On Apr 22, 4:13 pm, Ruben Willems <[email protected]> wrote: > > Hi > > > > this issue is fixed in the 1.4.4 RC1, > > you can set extra options on the project to handle the sourcecontrol > error > > handlinghttp:// > confluence.public.thoughtworks.org/display/CCNET/Project+Confi... > > > > options : > > maxSourceControlRetries > > stopProjectOnReachingMaxSourceControlRetries > > sourceControlErrorHandling > > > > I'm planning on releasing 1.4.4 RC1 tomorrow. > > > > with kind regards > > Ruben Willems > > > > > > > > On Wed, Apr 22, 2009 at 4:06 PM, Petros Amiridis <[email protected]> > wrote: > > > > > I have just upgraded to 1.4.3 from a previous version. It is possible > > > that this problem existed in previous versions too, and I assume based > > > on the release notes of 1.4.3 that previous versions just didn't > > > reported the SVN errors. Now, not only it reports the exception, but > > > also it leaves the project as broken. In fact, someone has to go and > > > trigger a force build for the project to get green again. > > > > > I can also confirm that this might happen when someone logs off and > > > CC.Net happens to check for modifications. I am saying this, because > > > for the last 4 days I no one logged into the CC.Net host server. > > > Today, I logged in to do some maintainance, and I got the SVN > > > exceptions in some projects (2 out of 15 or so). Furthermore, I am > > > using Remote Desktop to log into the CC.Net host server. I am also > > > using Subversion 1.5.4. > > > > > I understand that we are at a point where we are trying to figure out > > > if it is SVN or CC.Net's fault. In the meanwhile, is there a way to > > > lower the SVN block error level that CC.Net uses to mark a build > > > broken? I am logging in to that server frequently and I don't want to > > > always have random projects broken. > > > > > Thanks- Hide quoted text - > > > > - Show quoted text -
