[ZD-19670] CloudBees customer reported that the quite period checkout be...

...haviour has anomolous logic that can result in failed builds

- This is likely where there is a delay between the build leaving the quiet period and the build starting
- If there is a commit during that period of time then the build may checkout an inconsistent state
- The solution is to use the time when the quiet period is completed as the timestamp for the checkout
- Obviously people may prefer the original behaviour in some cases
Mind you, I agree that the behavior of the quiet period you describe seems poor. (And the CVS plugin should feel free to reinterpret the behavior of the quiet period, since this feature is pointless for any modern SCM—it was introduced for the benefit of CVS users.) I am just questioning what the purpose is of making this behavior conditional on `SCMTriggerCause`. IIUC, if you specify `delay=0sec` the quiet period is ignored anyway.