I have just upgraded from TFS2010 to TFS2013. The upgrade is also done on the build controller/agent.
Finalbuilder updated to build 7.0.0.2671 at the same time (on build controller/agent also).
On my TFS build definition I changed the process template from "FinalBuilderBuild.xaml" to "TfvxFBOnlyTemplate.12.xaml". This required me to fill out a few parameters that did not convert.
Restarted build controller.
When running a build I get the following error:
"Exception Message: There is no working folder mapping for M:\Builds\1\MyProject\MyBuildDefName\src. (type ItemNotMappedException)"
In the log I can see this happens in the "Assign - Version Control" action (I assume this is an "action" that is internal as it is not in my script).
In my build definition I map three different folders under "Source settings - working folders". This seems to be understood fine by TFS as it downloads these folders just fine.
The folder listed in the exception would be the "top level" folder for the full project (including all branches) and mapping this folder would cause 100000+ files to be downloaded.
In testing here locally I can not reproduce what your seeing. Our setup however wasn’t an upgrade, it was a straight installation. To help me further diagnose this issue please send through your TFS diagnostic log to support.
Having just performed a TFS 2010 to TFS 2012 upgrade I can confirm the error. In my case I had the following situation:- Migration from TFS 2010 to TFS 2012 with new hardware with the new associated hardware name. Migration of TFS from a “Developer Group Domain” to the “Corporate Domain”. Aka. Integrated security for developers. I switched off old TFS 2010 server.
Steps to resolve. Imported TFS 2010 collections to TFS 2012. Determined the name of the TFS 2012 build agents differed to the previous server one. Opened the $\Project\Branch*.sln in Visual Studio. Edited the \SolutionItems*.testSettings file being used in the TFS Build -> {My well named Build} -> Edit Build Definition -> 2. Basic -> Automated Tests -> Run Settings File -> “$/Project/Branch/*.testSettings” Changed the hard coded Roles -> Controller to use the new TFS 2012 server Controller fully qualified domain name.
In summary it looked like my new TFS server was trying to use my old TFS Servers Build Agent and then getting the changed directory structures mixed up.
Mental note: TFS build process and configuration is a PITA.
So for completeness and after seeing JenasysDesign post the issue I thought I should update this post.
The issue Lars was seeing was caused by an old design choice made in the upgrading of our TFS 2012 workflows to TFS 2013.
Previously we required the based directory of the repository to be mapped for the build. This was done so that we could get the mapped location of the FinalBuilder script and other files on the Agent. Previously there was a nice workflow action which allowed us to get this information from TFS 2012, however it was removed in TFS 2013.
In FinalBuilder 7.0.0.2795 I updated the TFS workflows by adding a new workflow action which we register when installing FinalBuilder. This new workflow allows us to get the mapped location of files on the agent without a base directory to work from being mapped.
This then subsequently removed the error of not having the base directory mapped when running the FinalBuilder workflow in TFS 2013.