>> 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.. > > ...and that's where our opinions differ: I see the situation as an actual > failure - if you aren't able to guarantee a successful build in a timely > fashion, it's a failure (along the lines of a typical "enterprise" SLA)... > just a question of filtering different failure notifications to different > people based on the cause. But then my opinion is just one of many, and > everyone is entitled to their own ;-)
Of course, and choice is good! Anyway, I took Ruben's advice about setting up a single queue for all our projects, and that should resolve the problem. I'm still not completely convinced that the underlying cause (svn log timeout) was due to the server or network, it may well be, but if more reports start coming in then there might be some other issue at work.
