[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title
Tomek Swiecicki commented on JENKINS-33487
Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
I am not sure this is related. I noticed that the plugin creates TFS workspace using the same TFS name but mapped to foldername and foldername@script depending of the step. By next step it detects the workspace is not mapped correctly local folder it deletes the tfs workspace and recreates it with a different local path. The build successful at the end, but it takes a long time to download the whole project twice. Why does it need to check-out 1627 resources just to read Jenkinsfile? Branch indexing Checking out hudson.plugins.tfs.TeamFoundationServerScm into c:\temp\workspace\xxx_Development@script to read Jenkinsfile Querying for remote changeset at '$/r/Development' as of 'D2019-11-08T09:10:18Z'... Query result is: Changeset #35974 by '' on '2019-11-07T19:34:04Z'. Checking if there exists a mapping for c:\temp\workspace\x_Development@script...no. Downloading list of workspaces from x xxx ... Creating workspace 'Hudson-Development-MASTER' owned by 'xx'... Mapping '$/xxx/Development' to local folder 'c:\temp\workspace\x_Development@script' in workspace 'Hudson-Development-MASTER'... Created workspace 'Hudson-Development-MASTER'. Getting version 'C35974' to 'c:\temp\xxx_Development@script'... Finished getting version 'C35974'. Retrieved 1627 resources.Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in c:\temp\workspace\xx2_Development[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutQuerying for remote changeset at '$/x/Development' as of 'D2019-11-08T09:10:18Z'... Query result is: Changeset #35974 by 'x' on '2019-11-07T19:34:04Z'. Checking if there exists a mapping for c:\temp\workspace\x_Development...no. Downloading list of workspaces from Warning: Although the server thinks the workspace exists, no mapping was found. Warning: The local folder is missing. Deleting workspaces named 'Hudson-Development-MASTER' from computer ''... Deleted 1 workspace(s) named 'Hudson-Development-MASTER'. Creating workspace 'Hudson-Development-MASTER' owned by ''... Mapping '$//Development' to local folder 'c:\temp\workspace\x_Development' in workspace 'Hudson-Development-MASTER'... Created workspace 'Hudson-Development-MASTER'. Getting version 'C35974' to 'c:\temp\workspace\_Development'... Finished getting version 'C35974'. Retrieved 1627 resources.[Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] withEnv[Pipeline] {[Pipeline] stage[Pipeline] { (restore)[Pipeline] batc:\temp\workspace\_Development>nuget restore ...
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Mark Piersak updated JENKINS-33487 Jenkins / JENKINS-33487 Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Change By: Mark Piersak Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168904.1457719657000.10063.1573049641716%40Atlassian.JIRA.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Mark Piersak started work on JENKINS-33487 Change By: Mark Piersak Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168904.1457719657000.10081.1573049641953%40Atlassian.JIRA.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Mark Piersak commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Is this issue being investigated, or has it been abandoned? Using the TFS plugin in a large scale environment does not work due to this bug. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168904.1457719657000.10053.1573048560871%40Atlassian.JIRA.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Pietro Pepe commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Currently I'm experiencing this issue on Jenkins 2.150.1 and plugin version 5.142.0. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Stu Farish commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 OK, I figured that part out. At least that makes it functional again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Stu Farish commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 "An easy workaround that has been used for several pipelines that have run into this issue is to rename the pipeline. Not ideal but can add a suffix or prefix to the pipeline until you run into the issue again. " I don't understand what that means? In terms of this, what's the pipeline? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Jake Wallace commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 An easy workaround that has been used for several pipelines that have run into this issue is to rename the pipeline. Not ideal but can add a suffix or prefix to the pipeline until you run into the issue again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Stu Farish commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 I'm also having the same issue with version v5.142 Mapping '$/AustalBS' to local folder 'C:\Program Files (x86)\Jenkins\workspace\AustalBSFreestyle\MEL' in workspace 'Hudson-AustalBSFreestyle-MASTER'... FATAL: com.microsoft.tfs.core.exceptions.TECoreException: The workspace Hudson-AustalBSFreestyle-MASTER;Stuart Farish already exists on computer AUSAT1SVTFS02. com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: The workspace Hudson-AustalBSFreestyle-MASTER;Stuart Farish already exists on computer AUSAT1SVTFS02. at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:117) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:987) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:665) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.createWorkspace(_RepositorySoap12Service.java:555) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:784) Caused: com.microsoft.tfs.core.exceptions.TECoreException: The workspace Hudson-AustalBSFreestyle-MASTER;Stuart Farish already exists on computer AUSAT1SVTFS02. at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:792) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1020) 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:1208) 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:1819) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Jake Wallace commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Having the same issue with version v5.142 Mapping '$/Projects/Configurator-SCM/Configurator-Wizard Dev' to local folder '/var/jenkins_home/workspace/PICAppDev/SCMWizardDev@script' in workspace 'Hudson-SCMWizardDev-MASTER'... com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: The workspace Hudson-SCMWizardDev-MASTER;dev_appdev_service already exists on computer ffaf3eb56301. at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:117) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:987) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:665) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.createWorkspace(_RepositorySoap12Service.java:555) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:784) Caused: com.microsoft.tfs.core.exceptions.TECoreException: The workspace Hudson-SCMWizardDev-MASTER;dev_appdev_service already exists on computer ffaf3eb56301. at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:792) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1020) 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 org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:290) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Sharon George commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 I am also experiencing this at TFS plugin v5.133. is there any resolution? we cannot continue running tf delete each time this happens... Thanks, Sharon Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel edited a comment on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 This issue is experienced in TFS Plugin v5.133 and TFS Plugin v5.139. Please see my above comment. Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel reopened an issue This issue is experienced in TFS Plugin v5.133 and TFS Plugin v5.139. Jenkins / JENKINS-33487 Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Change By: Monil Patel Resolution: Done Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title
Monil Patel edited a comment on JENKINS-33487
Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
We are experiencing the similar issue with TFS Plugin v5.133.0 and Cloudbees Jenkins v.2.89.4.2. Below is the Console output{code:java}Started by user XYZStarted by user XYZLightweight checkout support not available, falling back to full checkout.Checking out hudson.plugins.tfs.TeamFoundationServerScm into /Jenkins_Home/jenkins/workspace/Project-2/Dev/Build-Proj2@script to read JenkinsfileQuerying for remote changeset at '$/ABC/DEF/HIJ/KLM' as of 'D2018-10-12T11:56:42Z'...Query result is: Changeset #2162775 by 'XYZ' on '2018-10-12T11:56:33Z'.Checking if there exists a mapping for /Jenkins_Home/jenkins/workspace/Project-2/Dev/build-pr...@script...no.Downloading list of workspaces from https://tfs.ABC.com/tfs/DEF...Creating workspace 'Hudson-Build-Proj2-MASTER' owned by 'XYZ'...Mapping '$/ABC/DEF/HIJ/KLM' to local folder '/Jenkins_Home/jenkins/workspace/Project-2/Dev/Build-Proj2@script' in workspace 'Hudson-Build-Proj2-MASTER'...com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: The workspace Hudson-Build-Proj2-MASTER;FirtName LastName (XYZ) already exists on computer 12345678SVRName. at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:117) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:987) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:665) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.createWorkspace(_RepositorySoap12Service.java:555) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:784)Caused: com.microsoft.tfs.core.exceptions.TECoreException: The workspace Hudson-Build-Proj2-MASTER;FirtName LastName (XYZ) already exists on computer 12345678SVRName. at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:792) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1020) 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 org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:143) at
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel edited a comment on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We are experiencing tht the similar issue with TFS Plugin v5.133.0 and Cloudbees Jenkins v.2.89.4.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel edited a comment on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We are experiencing a tht similar issue with TFS Plugin v5.133.0 and Cloudbees Jenkins v.2.89.4.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We are experiencing a similar issue with TFS Plugin v5.133.0 and Cloudbees Jenkins v.2.89.4.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Mark Piersak updated an issue Jenkins / JENKINS-33487 Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We are experiencing the same issue as Jamie Nolan. Same exact plugin version 5.139.2 and Jenkins 2.121.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Jamie Nolan commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 I'm experiencing this same issue using plugin version 5.139.2 and Jenkins version 2.121.2 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title
Delicia Brummitt commented on JENKINS-33487
Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
This issue happens for TFS installed on Linux as well. The workaround is to change the name of the Project in Jenkins (changing the path). Some of the things that were tried (and failed)
deleting workspace via command line
deleting workspace via Visual Studio
clearing local cache in /home/ {user} /.microsoft/...
The plug-in seems to be using some cache for mapping that isnt used by Visual Studio and isnt used by the command line distribution.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Peter McEvoy commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Happening a lot more recently.. Seems that even after deleting the cache, I need to restart the agents that were using those workspaces. I definitely like not having to setup a tf.exe on the remove slaves, but I'm really not a fan of having to manually clean up caches and restarting remotely... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Will Saxon commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We just ran into this with a Jenkins instance running as Local System on Windows, with v4.0.0 of the TFS plugin. Just deleting the 'bad' workspace entries with 'tf workspace /delete' is not enough; as noted by posix phonix there is a cache file on the system which must be also cleaned up. The Local System profile is at %WINDIR%\system32\config\systemprofile. We were able to edit %WINDIR%\system32\config\systemprofile\AppData\Local\Microsoft\Team Foundation\4.0\Cache\VersionControl.config on the problem host to remove the bad workspace entries, restart the Jenkins agent and then rerun our build. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
