Hi <quote> I now have 7 projects in "Exception" status (which are actually running) with failed builds and none of them have actually failed, they only failed because our server wasn't able to query svn because another build appears to have saturated available resources on the server.. </quote>
do you use queues ? If you place all these projects in the same Q, but with a different Q priority, only 1 project will query the source control server at a given time. The other projects will wait there turn. That's the main reason CCNet has queues. with kind regards Ruben Willems On Tue, Mar 24, 2009 at 4:29 AM, si <[email protected]> wrote: > > Hi Sam, > > > My opinion: an error is an error... either the build succeeds or it > fails, > > Except the build was never actually triggered, it failed because the > trigger to test build conditions failed. > > I now have 7 projects in "Exception" status (which are actually > running) with failed builds and none of them have actually failed, > they only failed because our server wasn't able to query svn because > another build appears to have saturated available resources on the > server.. > > ... > > * Some tasks may need a little work to add options for robustness > > (configurable timeouts & retries). > > And that's all I really need to handle this edge case; improved > robustness for the intervalTrigger, although a separate publisher for > trigger-based exceptions wouldn't go astray. >
