Hi all, We have over a dozen projects in our source control repository (SVN) that share common code via SVN externals. Currently, when a developer check-ins a modification to the shared code, it causes CruiseControl.NET to build these dozen or so projects simultaneously. This tends to bog down our build server quite a bit.
To help stagger the builds a bit, I set different IntervalTrigger timings (<intervalTrigger seconds="120" />, <intervalTrigger seconds="140" />, etc.) to try to stagger the build start-ups when a modification is detected in SVN. However, after making this config (and even restarting the CC.NET service just in case), I still see these dozen or so projects starting up nearly simultaneously. At least 5 builds are starting in the same second despite having vastly different IntervalTrigger timings (30 seconds, 360 seconds, 120 seconds, etc.). Is the IntervalTrigger timing not being honored, or am I doing something completely wrong? Is this the correct way to stagger build starts for projects building on the same machine? Thanks! Russ
