vcs patch version out of sync

Hi,

Is there any way to force TeamCity to use a "baseline" source control patch when running a build?

We use TFS for source control and recently migrated from one machine to another, doing a branch and some other changes on the new source control machine. TeamCity was not running during this process and was also later migrated to a new machine. Now I find the source that TeamCity is using to build isn't the same version as what's on the server (basically the patching process has gotten out of sync). We're seeing a bunch of folders in the checkout directory that shouldn't be there and I'd like to clean them out.

As far as I can tell, the only way to remedy this situation is to do surgery on the database. Is there any easier way?

Thanks

10 comments
Comment actions Permalink

First of all try to invoke "Enforce clean checkout" action for the broken build configurations (see "Actions" menu at the build configuration home page).

0
Comment actions Permalink

Same results. Any other ideas?

0
Comment actions Permalink

What version of TeamCity you are using?

0
Comment actions Permalink

TeamCity Professional Version 4.0 (build 8080)

0
Comment actions Permalink

There were some improvements in TFS support in 4.0.2. Please try to upgrade to this version.

0
Comment actions Permalink

Upgraded, no bones.

0
Comment actions Permalink

This problem persists after the upgrade to 4.0.2. I tried a "Enforce clean checkout" on the build and it didn't make a difference.

What's the next step?

0
Comment actions Permalink

Could you please try checkout on agent?
Please node, you need to have Team Explorer installed on build agent machines.

0
Comment actions Permalink

I ran a build with:
VCS checkout mode: Automatically on Agent

and the version of the folders that was downloaded was what I was expecting to see (they were synched with source control).

I then ran another build with:
VCS checkout mode: Automatically on Server

and the version of the folders that was downloaded was the out of sync version I've been complaining about.I've been using the default (Automatically on Server) for all our builds.

I'm not really sure what the differences are here...I'm assuming Automatically on Agent has a different mechanism for keeping in sync with source control and wouldn't be using the db tables that are out of sync?

0
Comment actions Permalink

On the agent we use TFS Workspaces and thus delegate all checkout logics to TFS.
On the server side we use TFS api and analize history of changes in order to find list of files that are needed to be updated.

Could you please attach logs of tfs commandline util to the issue at
http://www.jetbrains.net/tracker/issue2/TW-6182
All instructions are placed added as comment.

Thanks!

0

Please sign in to leave a comment.