Hi those settings should work I used similar ones, and it works great
another approach is to use a filter trigger http://confluence.public.thoughtworks.org/display/CCNET/Filter+Trigger with kind regards Ruben Willems On Thu, Aug 26, 2010 at 2:34 PM, kowrip <[email protected]> wrote: > > We are having a similar problem with Perforce. The server is > unavailable each night when we run our maintenance scripts. When I > get in the next day, all of the projects have "Exception" status. I > need to manually force build them all. How have the new settings > worked for you ? We might need to tweak ours, too. > > > On Aug 11, 9:14 am, Chris <[email protected]> wrote: > > OK, > > > > I went with : > > > > <sourceControlErrorHandling>ReportOnRetryAmount</ > > sourceControlErrorHandling> > > <maxSourceControlRetries>6</maxSourceControlRetries> > > > > On the basis that the trigger interval of our projects is 10 minutes > > so that should give us a clear hour to get the SVN server back up > > before the project fails. > > > > On Aug 10, 4:13 pm, Chris <[email protected]> wrote: > > > > > > > > > Hi Daniel, > > > > > Thanks for your reply. Sorry I'm so late coming back to you. I > > > didn't get a mail notification to say that somebody had replied. > > > > > I currently don't set any of those properties, so according to my > > > interpretation of the documentation the project should automatically > > > keep on retrying over and over (and failing), until the SVN server > > > comes back up again and it should then reconnect and work > > > automatically. But it doesn't. Instead, as I said previously, I have > > > to walk through all of the projects one by one forcing them once the > > > server is back up. Is this a bug, or am I misinterpreting the docs? > > > > > Cheers, > > > > > Chris. > > > > > On Jul 30, 2:01 pm, Daniel Nauck <[email protected]> wrote: > > > > > > Hello, > > > > > > have a look at our <project /> block documentation [1]. > > > > > > You're looking for: > > > > -maxSourceControlRetries > > > > -sourceControlErrorHandling > > > > -stopProjectOnReachingMaxSourceControlRetries > > > > > > Daniel > > > > > > [1] > http://confluence.public.thoughtworks.org/display/CCNET/Project+Confi... > > > > > > Am 30.07.2010 09:48, schrieb Chris: > > > > > > > Hi guys, > > > > > > > I have a niggling problem with CC.net (1.4.4.83). Our CC server > and > > > > > ourSVNserver are both virtualised and running on separate machines > > > > > and occasionally theSVNhost is taken down for maintainance. When > > > > > this happens all of the CC projects based on interval triggers > (about > > > > > 40 of them) fail with anSVNexception. Reasonable I suppose, but > the > > > > > only way I can seem to bring them back to life after theSVNserver > 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. >
