-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.89.3
TFS-plugin 5.126.0
matrix-plugin 1.12
When using the TFS-plugin in combination with the Matrix plugin the first build of the projekt worked fine. But every new build of the same projekt throws this error:
FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path D:\jenkins\workspace\All_Targets\target\KDF is already mapped in workspace Hudson-target=KDF-KP0025_VisualStudio_VM;24865124-d1ea-4545-8285-2de5a102bff6.
There exists a workaround for this problem by deleting the workspace manually before building the project. But a solution would be desirable.
[JENKINS-49619] Team Foundation Sercer plugin error: workspace is already mapped
Component/s | Original: matrix-project-plugin [ 18765 ] |
Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] | New: redsolo [ redsolo ] |
Comment |
[ I am using plugin version [5.133.0|http://auto-hub:8080/pluginManager/plugin/tfs/thirdPartyLicenses] and also experienced it on 5.126.0 {code:java} // Mapping '$/QA/iTrak/iTrak12' to local folder 'C:\wrkspc\iTrak(multi-browser)' in workspace 'Hudson-iTrak(multi-browser)-MASTER'... FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi-browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson-SELENIUM_DRIVER=Windows_10chromelatest-MASTER. com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi-browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson-SELENIUM_DRIVER=Windows_10chromelatest-MASTER. at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:229) at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:176) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1014) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:950) at hudson.plugins.tfs.model.MockableVersionControlClient.createWorkspace(MockableVersionControlClient.java:114) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:81) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:24) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233) Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Workspaces.newWorkspace(Workspaces.java:109) at hudson.plugins.tfs.actions.CheckoutAction.getProject(CheckoutAction.java:144) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:59) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:352) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE {code} ] |
Assignee | Original: redsolo [ redsolo ] |
Nothing to do ion the Matrix Project side from what I see. I had issues with that in 2012 and worked around by using custom workspace names, but generally the plugin should have logic to prevent that