New intervalTrigger behaviour after upgrading from 1.4 to 1.4.4

[cruiseDk]

After upgrading to 1.4.4 I have a problem with the intervalTrigger
when access to VSS gives an exception. Our VSS is not very stable an
sometimes it throws exceptions like:

ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control
operation failed: Unable to open user login file \\****\data\loggedin
\***.log

1.4 did not register this as a failure to the project (another check
was done 60 seconds later and everything was fine)

<triggers>
<intervalTrigger seconds="60" />
</triggers>

With 1.4.4 the "Last Build Status" changes to "Exception" if the VSS
check fails. Even worse, later successful checks will not put the
status back in "Success" (because no changes have been made, hence no
builds are required)

Is the there an option to ignore exceptions from VSS in the
intervalTrigger?

[Ruben Willems]

Hi

yes there is
look in the release notes item :

More control on Source Control Exceptions

You have now more control on the behaviour when the source control has
problems getting the modifications.
Look at Project configuration for the following settings :
° maxSourceControlRetries,
° stopProjectOnReachingMaxSourceControlRetries
° sourceControlErrorHandling.

http://confluence.public.thoughtworks.org/display/CCNET/Project+Configuration+Block

with kind regards
Ruben Willems

[cruiseDk]

Thank you. I added <sourceControlErrorHandling> to the <report> node
and it seems like it did the trick.

<sourceControlErrorHandling>ReportOnRetryAmount</
sourceControlErrorHandling>

Regards

Stig