@Reuben: Yes, 20 should be enough! I set it that high because I wanted
to see if it made any difference. I might turn it down a bit later on.
Regarding the netword/source control server. In this particular
project we are using a hosted source control solution so it is out of
our hands. But I can say we have never had any problems like this
before. It all started after I upgraded to the latest version of
CCNET. Thanks for all the help! I'm keeping my fingers crossed that it
will continue to work.

On 2 Juli, 08:31, Ruben Willems <[email protected]> wrote:
> Hi
>
> let's hope so [?]
>
> you've configured to only report when there are 20 consecutive source
> control connection problems
> so that should be more than enough.
>
> If you now have a failed build, due to a source control problem,
> I would advise to check the stability of the network / source control
> server.
>
> with kind regards
> Ruben Willems
>
> On Thu, Jul 2, 2009 at 8:22 AM, Kristoffer Ahl <[email protected]> wrote:
>
> > @Phil: Yes, I have the Collabnet Subversion client installed as well
> > as SlikSvn client. However, I did not have them both when the error
> > started to occur.
>
> > @Ruben: I've added <maxSourceControlRetries>20</
> > maxSourceControlRetries> and
> > <sourceControlErrorHandling>ReportOnEveryRetryAmount</
> > sourceControlErrorHandling> to my CC-config for the broken projects
> > and since I haven't had the build fail. I'm crossing my fingers that
> > this is all I needed to do. Thanks!
>
> > On 29 Juni, 20:55, "Phil Sayers" <[email protected]> wrote:
> > > Do you have Subversion Server & Client installed (from collabnet) on the
> > > same machine as the SlikSvn client?
>
> > > Are both the collabnet-svn client AND SlikSvn-client linked to the exact
> > > same version of subversion?
>
> > > I've  had problems when I've mixed the collabnet client & server svn
> > > software with an installation of TortoiseSvnClient which is linked to a
> > > different version of svn than the collabnet binaries.
>
> > > Also, if you've upgraded either the collabnet or sliksvn software... I've
> > > found I typically have to delete & re-create any svn working copies that
> > are
> > > used by ccnet in the workspace of each build, otherwise I have a scenario
> > > like the one you describe here.
>
> > > -----Original Message-----
> > > From: [email protected] [mailto:[email protected]]
> > On
>
> > > Behalf Of Craig
> > > Sent: Monday, June 29, 2009 6:29 AM
> > > To: ccnet-user
> > > Subject: [ccnet-user] Re: CruiseControlException when connecting to
> > source
> > > control
>
> > > 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.GetModifica
> > > tions
> > > > (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!
>
>
>
>  328.png
> < 1KVisaHämta

Reply via email to