All geek questions in one place

CruiseControlException when connecting to a control source

I get an exception from Cruise Control about the impossibility of connecting to the server. However, if I force the build, it works fine. I also tried using the repository to connect to the server without any problems, so I know that the server is up and running. I am running CCNET 1.4.4 and SlikSVN 1.5.3. The following is an exception to 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 log https://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!

+4
source share
2 answers

Finally, I started working again, and this is what I did.

  • Set maxSourceControlRetries to 10 in my CCNET-config
  • Set sourceControlErrorHandling to ReportOnEveryRetryAmount in my CCNET-config
  • Switched to the latest CollabNet client

As it turned out, CCNET swallowed source errors like these in previous versions, so I might have problems even before I upgraded to CCNET 1.4.4, but didn't know about it.

Thanks for your comments!

+5
source

I ran into this problem when changing SVN source next to code freeze. I create a release tag and modify the source control section to refer to the tag, and not to the development branch. However, the assembly working directory will still contain the source for the development branch, including all SVN metafiles. This throws an exception due to a clash of SVN sources (the original dev branch and the new release tag).

In this case, a simple solution is to remove the code (directories and everything) from the working directory of the assembly , and CruiseControl to pull the source for the development branch from a new location.

Here is an excerpt from the ccnet.config file that has been modified to cause this problem. Does this look familiar?

 <sourcecontrol type="multi"> <sourceControls> <svn> <!-- <trunkUrl>https://svn/Engineering/Applications/Quasar/branches/TeamRowdy</trunkUrl> --> <trunkUrl>https://svn/Engineering/Applications/Quasar/tags/REL-TeamRowdy-RC1-2013.07.17.003</trunkUrl> <workingDirectory>Quasar</workingDirectory> <cleanUp>true</cleanUp> <forceUpdate>true</forceUpdate> </svn> <svn> <!-- <trunkUrl>https://svn/Engineering/Applications/Acme/branches/TeamRowdy</trunkUrl> --> <trunkUrl>https://svn/Engineering/Applications/Acme/tags/REL-TeamRowdy-RC1-2013.07.17.003</trunkUrl> <workingDirectory>Acme</workingDirectory> <cleanCopy>true</cleanCopy> </svn> </sourceControls> </sourcecontrol>
0
source

Source: https://habr.com/ru/post/1286612/

More articles:


All Articles