TeamCity is not retrieving all files from SubVersion

Question

I'm in the process of setting up a QA server using TeamCity. I've just added a project and its configuration to TeamCity, but have noticed that it's not getting all the files from one of the VCS roots I have set up.

Other projects are not having this problem, and neither is this projects failing to retrieve any files at all from the root in question. It is a small number of DLL files in the /website/bin subdirectory of the VCS root in question.

The build log doesn't hint at there being any problems here:

[11:43:46]: [Updating sources: server side checkout...] Building incremental patch for VCS root: website-static

is all the log mentions.

Compiling doesn't have any problems, and only when the site, which is built on Umbraco, is browsed to, does the fact that Microsoft.ApplicationBlocks.Data.dll (amongst others) has not been retrieved come to light.

There are other Umbraco based sites already set up on this server that are not experiencing this.

Does anyone have any suggestions as to what might be going on, or at least where I could start looking?

Many thanks in advance.

Answer 1

In my case(team city server 8.0.3) we had a strange situation when team city didn't update part of external svn folder. Based on release note of 8.0.4 server there was issue, related with externals work: http://youtrack.jetbrains.com/issue/TW-31507, but upgrade to new server didn't help too.

The solution was the switching of external setting for VCS root from "Full support (load changes and checkout)" to "Checkout, but ignore changes". After it our external folder was updated correctly.

Hope this help to resolve such kind of issues.

Answer 2

At the risk of looking bad for answering my own question here, I'm going to have to say there was no answer to this strangeness. Eventually, I gave up, as it was taking too much time to be justified for such a small, if perplexing, issue. The workaround has proved to be a manual check out when required.

Answer 3

Sometimes you have to kick it to make it run. :-) When we experience this type of behaviour, we select "Enforce clean checkout" in the build configuration view, and then press Run again.

Answer 4

If there are checkout rules in the VCS Root under Version Control settings for your configuration, they maybe selectively checking out only certain parts of the root which did not include /website/bin

Can you do a clean of the checkout and try it again? It is done from the Version Control settings: