Apologies if this is totally not the appropriate venue....

I've posted over at the codeplex site for the TFS plug in and haven't
gotten any responses. Has anyone actually gotten TFS 2008 support to
work?

This is what I have in TFS history for the ccnet.config file (which is
being downloaded to a directory other than the configured directory):
36333   edit    laadams 3/6/2009 11:58:58 AM
36332   edit    laadams 3/6/2009 11:56:13 AM
36331   edit    laadams 3/6/2009 11:50:27 AM
36330   edit    laadams 3/6/2009 11:46:41 AM
36329   edit    laadams 3/6/2009 11:43:37 AM
36327   edit    laadams 3/6/2009 11:30:57 AM

Now my CCNET server is in a different timezone, so the log file
entries are all 1 hour off.
2009-03-06 11:09:20,914 [cc-config:INFO] Project: 'cc-config' is added
to queue: 'cc-config' in position 0.
2009-03-06 11:09:21,023 [cc-config:INFO] Project: 'cc-config' is first
in queue: 'cc-config' and shall start integration.
2009-03-06 11:09:21,023 [cc-config:DEBUG] Checking Team Foundation
Server for Modifications
2009-03-06 11:09:21,023 [cc-config:DEBUG] From: 3/6/2009 10:57:49 AM -
To: 3/6/2009 11:09:21 AM
2009-03-06 11:09:21,711 [cc-config:DEBUG] Found 1 modifications
2009-03-06 11:09:21,711 [cc-config:INFO] 1 modification detected.
2009-03-06 11:09:21,711 [cc-config:INFO] Building: config-continuous
triggered a build (IfModificationExists)
2009-03-06 11:09:22,304 [cc-config:DEBUG] Existing workspace detected
- reusing
2009-03-06 11:09:22,523 [cc-config:DEBUG] Getting $/CMS/branch/ccnet/
config to C:\Program Files\CruiseControl.NET\server\cc-config
2009-03-06 11:09:22,523 [cc-config:DEBUG] Performing a Get Latest

So you see it's finding a modification the modifications and
attempting for all the world to retrieve it. If I go look at the
timestamp of the physical file though, it has a modification date of
10:31AM and the contents match those of the 10:30:57AM version of the
file, so none of the 5 modifications after 10:30:57AM were actually
downloaded from source control. The maddening thing is, it seems to
sporadically work, since it obviously got the 10:30:57 version!

Through experimenting the last couple days, I've discovered that if I
have the file open in something that locks it, I will get an error in
the log complaining that the file couldn't be replaced because it was
in use -- which was actually my first thought about what might be
going on.

Any suggestions? Beyond of course the obvious "don't use VSTS"  --
nary a day goes by without me wishing I could take it out back and
shoot it.

Reply via email to