The TFS plugin sometimes includes changesets in the "Changes" list that were not actually included in the source that was built. Those changes end up getting reported again (correctly) in the next build.

This is pretty easily seen in the timestamps used for the "tf history" commands. Here are two consecutive builds. Note how the end time for the history command in build #1738 (17:18:36Z) is after the start time for the history command in build #1739 (17:04:31Z). Shouldn't those two times be the same?

 
build #1738
[workspace] $ tf history $/Checkpoint/Web/Application/main -noprompt -version:D2010-05-21T15:59:25Z~D2010-05-21T17:18:36Z -recursive -format:detailed -server:http://tfstta.int.thomson.com:8081 ********

build #1739
[workspace] $ tf history $/Checkpoint/Web/Application/main -noprompt -version:D2010-05-21T17:04:31Z~D2010-05-21T17:53:54Z -recursive -format:detailed -server:http://tfstta.int.thomson.com:8081 ********

My guess is that the end time for the "tf history" command is incorrectly using the current time, when really it should be using the start time of the current build (or more precisely, probably the instant that the "tf get" command was run).

Note: we are doing a complete "get" of our source code each time ("use update" flag is not checked) which is apparently taking quite a while (14 minutes) on our admittedly slow build machine.

Side note: We turned off "use update" because we had a situation where a deleted file in TFS did not get deleted in the workspace...I suppose that should be a different bug report, unless it's already been fixed...