TFS plugin mapping conflict

[Andy Falanga]

Hello all,

I recently updated my TFS plugin to version 4.0.0 to take advantage of the Java client instead of having to install a tf client on all my Linux hosts.  I have two Linux build agents and the Jenkins server runs on Windows.  I occasionally see problems like this:

FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException:
The path /home/builder/jenkins/workspace/LinuxBuildCompileOnly is already mapped in workspace Hudson-LinuxBuildCompileOnly-devlnx64-04.

This occurred on host devlnx64-03.  What is causing this?  A review of the log shows the following:

Deleting workspaces named 'Hudson-LinuxBuildCompileOnly-devlnx64-03' from computer 'devlnx64-03'...
Deleted 1 workspace(s) named 'Hudson-LinuxBuildCompileOnly-devlnx64-03'.
Creating workspace 'Hudson-LinuxBuildCompileOnly-devlnx64-03' owned by 'WINNTDOM\umtfsservice'...
Created workspace 'Hudson-LinuxBuildCompileOnly-devlnx64-03'.
Mapping '$/Project/Main' to local folder '/home/builder/jenkins/workspace/LinuxBuildCompileOnly' in
 workspace 'Hudson-LinuxBuildCompileOnly-devlnx64-03'...

The process removes the old workspace and remakes it.  Why is TFS complaining about this mapping?  Shouldn't it be content to allow the TFS location to be mapped to more than one location on different systems and in different workspaces?  I'm quite curious about this and would appreciate any insights those here might have.

Thanks,
Andy

[Stefan Drissen]

I had issues when the workspaces already existed in 3.2.0 - see https://issues.jenkins-ci.org/browse/JENKINS-30355

Not sure if this is the same as your issue - in my case deleting the old workspaces first solved the issue. After that I ran into a number of other issues with the 4.0.0 plug-in and downgraded back to 3.2.0

Regards,

Stefan