I have Team Foundation Server 2008 Installation and a separate computer with Team Build.
I can create an assembly of commands and run them manually in Visual Studio or through the command line (where they complete successfully). However, the ins check in the source tree does not cause the assembly to start, despite the possibility of creating each check in a tick on the assembly definition. Update. To be clear, I had a fully working assembly definition with the CI option turned on.
The source tree is configured fairly straightforward with the code either in the main folder or in the Branch \ branchName folder. Each branch of code (including the main one) has a standard Team Build definition that refers to the solution file contained inside. The only thing that slightly changed from the default settings is that the working folder of the build server; those. for main, this is the server: "$ \ main" Local: "c: \ build \ main" due to the path length.
The only thing I could guess (a possible red herring) was that there might be some kind of weirdness in the developer workspaces. Currently, each developer maps Server: "$ \" to local: "c: \ tfs \", so that for all branches there is only one workspace. This is mainly in order to avoid the cross-mapping problems that were previously used by some developers. But I do not see how this will affect CI.
UPDATE: tap the answer indirectly; please read below
source
share