other cache locations

Hi,

is the folder ".BuildServer\system\caches" the only location where Teamcity caches files checked out from a VCS  ?
Or is it possible that some files are also cached on the agent ?  What I don't understand :  if I delete a file in the VCS and delete the cache directory on the server, the deleted file gets transfered to the agent anyway. (I can watch on the agent how the checkout folder gets deleted (clean checkout) and then is created again with the file that should not exist any more).   

So where could be the location where Teamcity get this old file version from ?

Thanks
fritz

5 comments
Comment actions Permalink

Fritz,

Could you please file this issue to our issue tracker  and provide the following  information:
  - Version control system
  - TeamCity version
  - server logs (TeamCity/logs/teamcity*.log)
  - build agent logs ( buildAgent/logs/*)

0
Comment actions Permalink

The cache exists to improve performance and to reduce load on VCS. If cache is deleted TeamCity will create it again. What you've done in VCS should be reflected in agent checkout directory independently of cached files, otherwise we would not be able to rely on TeamCity.

What is the problem with cache? Why do you need to cleanup it?

0
Comment actions Permalink

Because I thought if the cache exists, TC maybe will not check out the newest  files from VSS, but use the old cached versions (I wrote two other threads related to this problem). Now we solved the problem by using the nant contrib task vssget, i.e. not let TC do the checkout.

Thanks

0
Comment actions Permalink

The problem with VSS might be caused by time sycnhronization issue - for VSS it is critical to have server and repository time in sync

0
Comment actions Permalink

Yes  we are using VSS 6.0 and Teamcity 5.0, but the time seems synchronized on both servers.

0

Please sign in to leave a comment.