TeamCity 6(build 15772) - not detecting changes from Team Foundation Server (TFS).

Hi,

The last few changes in TFS are not showing as changes in TeamCity and the new files are not being checked out.

I can see the changes if I browse through Visual Studio / Source Control, and see the history of the file in question.

But on the build agent, the old version of the file is present and the revision number for the build as a whole is not the latest.

I remember playing with the clean all files setting to make it work last time, but its still not working now.

Have gone to the agent page and forced it to remove all local files - but thats still pulled down the old code :(

Its definitely pulled the code from somewhere, as the timestamp has been updated, but its not the latest version.

I can go to the VCS page for this link and the Test connection button seems to work ok.

Any thoughts on what might be going wrong.

Thanks,
Chris

5 comments
Comment actions Permalink

Hi Chris

We've just fixed similar issue in 6.0.2 - TW-15052
Can you upgrade and check whether it helps.

Thanks
Michael

0
Comment actions Permalink

Hi,

I have just upgraded to 6.0.2 (build 15857), but its not helping.

It shows no changes.

We use "checkout on server" and I did a clean sources on the agent.

I noticed some comments about case sensitivity issues in the linked bug - double checked and I had a capitalised word when I shouldnt have.

Now it seems to be working fine.  I guess that wasnt fixed (or its just not meant to work that way...)

I notice the "Test connection" option in the VCS root takes either way as valid, when only 1 really works when doing a build... is there a bug raised for that?

Thanks,
Chris

0
Comment actions Permalink

Chris

Could you tell what settings have you changed to get it working, and how.
I would like to reproduce this issue in my lab.

Thanks

0
Comment actions Permalink

Hi,

In the VCS settings, the TFS path was something like $/.../Development/...  but should have been $/.../development/

If I change it back and forth, and do "Test Connection", then it seems ok.

But running an actual build, it does not pickup code changes when the case is wrong.

I am not sure of our TFS version - probably 2008...

Thanks,
Chris

0
Comment actions Permalink

Just ran into this as well.  Case matters for the TFS Root path.

0

Please sign in to leave a comment.