@Reuben
Yes, that sounds about right. After a build has been broken, all I
need to do is to force a build and it's all good again. But as you
wrote, it usually takes a little time for me to get notified of the
error. I should have mentioned that the problems started after we
upgraded from CCNET 1.4.(0 or 1) to CCNET 1.4.4.
Thanks for the tip on sourceControlErrorHandling!

On 29 Juni, 14:02, Ruben Willems <[email protected]> wrote:
> Hi
>
> so let's say 90% of the time the build goes ok,
> when you see this error you do a force build and all is ok again?
>
> probably there  is some time between you noticing the problem and pressing
> the force build
> --> this appears to be a temporarily error, although appearing a lot
>
> in version 1.4.4 you can control what to do with these kind of errors
> see the project configuration 
> blockhttp://confluence.public.thoughtworks.org/display/CCNET/Project+Confi...
>
> sourceControlErrorHandling
>
> with kind regards
> Ruben Willems
>
> On Mon, Jun 29, 2009 at 1:56 PM, Kristoffer Ahl <[email protected]> wrote:
>
> > Yes, that is what I thought as well but when I do a force build
> > everything works as expected (including getting the source code). The
> > build can be ok for a couple of hourse but it seems like it crashes
> > once a day for the same reason (I have no daily builds configured).
>
> > On 29 Juni, 12:28, Craig <[email protected]> wrote:
> > > Normally this is a security error, i.e. the service cannot access the
> > > Subversion server, but it is weird that you can force build it. When
> > > you force build, is it retrieving the code from the repository?
>
> > > Craig
>
> > > On Jun 29, 7:37 pm, Kristoffer Ahl <[email protected]> wrote:
>
> > > > I'm getting an exception from Cruise Control about not being able to
> > > > connect to the server. However, if I force a build it works just fine.
> > > > I've also tried using the repo-browser to connect to the server
> > > > without any problems so I know that the server is up and running. I'm
> > > > running CCNET 1.4.4 and SlikSVN 1.6.3. Below is the exception from the
> > > > CCNET log:
>
> > > > ThoughtWorks.CruiseControl.Core.CruiseControlException:
> > > > Source control operation failed: svn: OPTIONS of 'https://some-
> > > > server.com/trunk': could not connect to server (https://some-
> > > > server.com) .
> > > > Process command: C:\Program\SlikSvn\bin\svn.exe loghttps://
> > some-server.com/trunk
> > > > -r "{2009-06-23T01:36:19Z}:{2009-06-23T07:20:25Z}" --verbose --xml --
> > > > username ccnet --password auto --non-interactive --no-auth-cache
> > > > at
>
> > ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute
> > > > (ProcessInfo processInfo)
> > > > at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.GetModifications
> > > > (IIntegrationResult from, IIntegrationResult to)
> > > > at
>
> > ThoughtWorks.CruiseControl.Core.Sourcecontrol.MultiSourceControl.GetModifications
> > > > (IIntegrationResult from, IIntegrationResult to)
> > > > at
>
> > ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications
> > > > (ISourceControl sourceControl, IIntegrationResult lastBuild,
> > > > IIntegrationResult thisBuild)
> > > > at ThoughtWorks.CruiseControl.Core.IntegrationRunner.GetModifications
> > > > (IIntegrationResult from, IIntegrationResult to) vid
> > > > ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate
> > > > (IntegrationRequest request)
>
> > > > Any ideas would be much appreciated!

Reply via email to