Vcs quiet period

Andrei,

Such option is available only for CVS VCS settings.
In general, TeamCity periodically polls for the modification in all configured VCS roots to detect changes. If change is available and VCS triggering is enabled, build goes to queue.
For CVS, you can configure a timout since last change after which build goes to queue.

With kind regards,
KIR

Hello Kirill,

The feature is very valuable for any VCS. For a number of reasons people
might commit in batches. Suppose you have a mixed C#/Java project and the
2 code bases must be in sync for the build to succeed. You won't have both
in IDEA and thus the commit will be in separate batches.
If TC doesn't support triggering the build only after a quiet period, it
would cause false failures and thus team annoyance (CruiseControl supports
that and it works quite well).

Please consider adding this for any VCS.

Thanks,
Raz

Andrei,

Such option is available only for CVS VCS settings.
In general, TeamCity periodically polls for the modification in all
configured VCS roots to detect changes. If change is available and VCS
triggering is enabled, build goes to queue.
For CVS, you can configure a timout since last change after which
build goes to queue.
With kind regards,
KIR

Sounds reasonable and filed as
http://www.jetbrains.net/jira/browse/TW-2154

Please vote :)

Regards,
KIR