Slow to detect changes in tfs despite rapid trigger

Topics: Developer Forum, User Forum
Sep 21, 2007 at 9:12 AM
I've just set up the lastest version of CCNet and the TFS-plugin with our projects, and things are going well.

But, one of our builds is supposed to trigger everytime changes are checked-in in tfs. This works ok, but the plugin does not seem to detect the changes before after 1-2 minutes after check-in from visual stuido, despite that the trigger interval is set to 5 seconds (And I see in the console that it really checks for changes: No changes detected). It seems like CCNet is doing its job, but doesn't get any reports of changes before after 1-2 minutes, then the get latest triggers. Have anyone experienced this delay or know where the problem lies, is there a delay in tfs causing this?

The reason for builds to trigger quickly is so our developer after check-in as asap will get the result of the build and unittests, before continuing to work on other issues.
Coordinator
Sep 21, 2007 at 4:15 PM
Is there a difference in the clocks between your build server and your TFS server? While you can have time zone differences between the two machines, a difference in the actual clock times might cause this problem.
Sep 24, 2007 at 5:36 AM
Hi,

thanks, this worked fine. One clock was synced against Internet, one not. This fixed the problem :)