I recently had a situation where it appeared that my 'Quiet Period' settings for triggering a build was ignored.
My build trigger is set as follows:
|Build Trigger ||Parameters Description
Quiet period: 180 seconds (custom)
So it should be waiting for 3 minutes before attempting to trigger a build, however this was not the case.
My setup can be simplified as follows:
'Frequent Build Trigger' (Quiet period trigger as above)
---- Which is snapshot dependent on "Execute Tests Debug PC"
---- ---- Which is snapshot dependent on 'Runtime Compile All Libs Debug PC'
So every time the frequent build trigger is initiated, it'll then kick off compilation steps I require, in order to run the tests, so that the trigger config itself can be ran.
In this odd case, the 'Frequent Build Trigger' config is claiming that it ran a single time between the hours of '13 Sep 12 15:38' and '13 Sep 12 17:46' with a total of 27 changes present in that build (see below) - This is correct
But it's 'Runtime Compile All Libs Debug PC' dependency is being somehow triggered by it more than that, note there's still 27 changes, but spread over three builds. (see below) - This is incorrect.
Looking at that first incorrect build (#143) - It's claiming that the 'Frequent Build Trigger' started that build, but I can't determine how.... and clues?
Any assistance with this issue would be great, because it's currently meaning we're compiling many redundant builds.