Here's the issue:

Our Build Server is separate from our SourceSafe Server. During our Daily Build process, from time to time, the Build machine will be unable to get access to the SourceSafe server to check code in or check code out. In my CheckIn tasks, I have the attribute failonerror="true". This causes my entire build process to fail (which takes about 25 minutes) and I have to start all the tasks over again.

<vsscheckin
user="${username}"
password="${password}"
localpath="${projectpath}/SolutionInfo.vb"
recursive="true"
writable="false"
dbpath="${ssdbpath}"
path="${ssrootprojectname}/SolutionInfo.vb"
failonerror="true"
comment="Build Label : ${sslabel}"/>

What I would like to do is set this attribute (failonerror="true") to "false" and then be able to check to see if an error has ocurred. If an error has occurred, I would like to Sleep for a few sections and try again up to 10 times before I finally fail the entire build all together.

Do you know how I can execute a Task and then check to see if it has failed?  What property do I need to check for after I have executed the task?  I would like to put the Task in a For loop and exit the loop if no error has occurred or above if my error count is greater than the number of failed attempts that I want to allow.

Thanks,

Chris

 

 

Reply via email to