Hi guys,

I have a niggling problem with CC.net (1.4.4.83).  Our CC server and
our SVN server are both virtualised and running on separate machines
and occasionally the SVN host is taken down for maintainance.    When
this happens all of the CC projects based on interval triggers (about
40 of them) fail with an SVN exception.  Reasonable I suppose, but the
only way I can seem to bring them back to life after the SVN server is
up again is to walk through them, forcing them one by one.  This can
get pretty tiresome after a few times.  Am I missing some
configuration setting somewhere that will automatically bring them
back up when the link is restored?  Or is there a way I can prevent
them from failing when the link goes down?  Here is a typical project
config...

<project name="Portal_Release">
  <workingDirectory>c:\Projects\ThreeG\Runtime\Portal</
workingDirectory>
  <modificationDelaySeconds>600</modificationDelaySeconds>
  <sourcecontrol type="multi">
    <sourceControls>
      <svn>
        <trunkUrl>https://ddcsvn01.internal.XXXXX.com/svn/engineering/
projects/ThreeG/Runtime/Portal/branch/Merge/Common</trunkUrl>
        <workingDirectory>c:\Projects\ThreeG\Runtime\Portal\Common</
workingDirectory>
        <cleanUp>true</cleanUp>
      </svn>
      <svn>
        <trunkUrl>https://ddcsvn01.internal.XXXXX.com/svn/engineering/
projects/ThreeG/Runtime/Portal/branch/Merge/WindowsNative</trunkUrl>
        <workingDirectory>c:\Projects\ThreeG\Runtime\Portal
\WindowsNative</workingDirectory>
        <cleanUp>true</cleanUp>
      </svn>
    </sourceControls>
  </sourcecontrol>
  <triggers>
    <intervalTrigger seconds="600" />
  </triggers>
  <tasks>
    <devenv>
      <solutionfile>Windowsnative\Portal.sln</solutionfile>
      <configuration>Release</configuration>
      <buildtype>Rebuild</buildtype>
      <executable>C:\Program Files\Microsoft Visual Studio
9.0\Common7\IDE\devenv.com</executable>
    </devenv>
    <exec executable="c:\Program Files\Windows Installer XML v3\bin
\candle.exe">
      <buildArgs>"WindowsNative\Developer Setup
\XXXXX.ThreeG.Runtime.Portal Developer Setup.wxs" -out "WindowsNative
\Developer Setup\XXXXX.ThreeG.Runtime.Portal Developer Setup.wixobj"</
buildArgs>
    </exec>
    <exec executable="c:\Program Files\Windows Installer XML v3\bin
\light.exe">
      <buildArgs>-ext WixUIExtension -cultures:en-us "WindowsNative
\Developer Setup\XXXXX.ThreeG.Runtime.Portal Developer Setup.wixobj" -
out "WindowsNative\Developer Setup\Release\XXXXX.ThreeG.Runtime.Portal
Developer Setup.msi"</buildArgs>
    </exec>
    <exec executable="msiexec.exe">
      <buildArgs>/x {43D21C82-BD61-4656-BAE2-C9F5BFD6E5A4} /passive /
q /norestart</buildArgs>
      <successExitCodes>0,1605</successExitCodes>
    </exec>
    <exec executable="msiexec.exe">
      <buildArgs>/i "WindowsNative\Developer Setup\Release
\XXXXX.ThreeG.Runtime.Portal Developer Setup.msi" REINSTALLMODE=amus /
q /norestart</buildArgs>
    </exec>
    <exec executable="7za.exe">
        <buildArgs>a D:\DeveloperInstallers\Portal\PortalSetup.zip "C:
\Projects\ThreeG\Runtime\Portal\WindowsNative\Developer Setup\Release
\*"</buildArgs>
      </exec>
  </tasks>
  <labeller type="defaultlabeller">
    <incrementOnFailure>False</incrementOnFailure>
  </labeller>
</project>


I really appreciate your time and support on this issue.

Regards,

Chris Chambers.

Reply via email to