Is there a way to configure a quiet period to control the frequency of checks against the feed in the NuGet Dependency Trigger (similar to the VCS trigger)? Our current build system has several hundred triggers across 110 build configurations and is choking a bit under the load, considering the dependency trigger runs solely on the TeamCity server (and not the agents).
Furthermore, following some minor investigation it seems that a new NuGet.exe process is spawned for each NuGet dependency trigger instance (please correct me if I'm wrong?). It would seem that this design doesn't scale well to an enterprise configuration with hundreds of triggers. The preference here would be to batch all the triggers within a build configuration to a single NuGet.exe list process and check the Package ID's then - I guess this would be the ideal solution instead of exposing a quiet period...
Hope that makes sense... and thanks in advance,