[JIRA] [tfs-plugin] (JENKINS-31875) No working folder mapping when accessing TFS (win 10)

46 views
Skip to first unread message

xstepl@gmail.com (JIRA)

unread,
Dec 3, 2015, 11:02:06 AM12/3/15
to jenkinsc...@googlegroups.com
Stephen Leung created an issue
 
Jenkins / Bug JENKINS-31875
No working folder mapping when accessing TFS (win 10)
Issue Type: Bug Bug
Assignee: redsolo
Attachments: tfsplugin.PNG
Components: tfs-plugin
Created: 03/Dec/15 4:01 PM
Environment: Win 10, Java 8, Jenkins 1.639, Chrome
Priority: Critical Critical
Reporter: Stephen Leung

1. Installed Jenkins on Windows 10
2. Added TFS Plug-in 4.0.0 (No choice to use earlier version)
3. Configured correct credentials to access TFS (Can access it via Team Explorer)

Result:
C:\Jenkins\jobs\sanityprod\workspace.
java.lang.RuntimeException: com.microsoft.tfs.core.clients.versioncontrol.exceptions.ItemNotMappedException: There is no working folder mapping for C:\Jenkins\jobs\sanityprod\workspace.
at hudson.plugins.tfs.model.Server.execute(Server.java:110)
at hudson.plugins.tfs.model.Project.getFiles(Project.java:177)
at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:54)
at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:221)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: com.microsoft.tfs.core.clients.versioncontrol.exceptions.ItemNotMappedException: There is no working folder mapping for C:\Jenkins\jobs\sanityprod\workspace.
at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.getLocalWorkspace(VersionControlClient.java:737)
at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.getWorkspace(VersionControlClient.java:2154)
at hudson.plugins.tfs.model.MockableVersionControlClient.getWorkspace(MockableVersionControlClient.java:93)
at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:57)
at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:17)
at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
at hudson.plugins.tfs.model.Server.execute(Server.java:106)
... 11 more

note: This same setup works fine in Win 8.1 with Java 1.7. Tried deleting workspace folder and repeating. Same problem occurred

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

james@jbrantly.com (JIRA)

unread,
Dec 3, 2015, 11:53:03 PM12/3/15
to jenkinsc...@googlegroups.com
James Brantly commented on Bug JENKINS-31875
 
Re: No working folder mapping when accessing TFS (win 10)

I found that I ran into this issue when there was a period in the workspace path. Changing the period to an underscore fixed the issue right up.

xstepl@gmail.com (JIRA)

unread,
Dec 4, 2015, 8:40:02 AM12/4/15
to jenkinsc...@googlegroups.com

Thanks James, this worked! I was just about to abandon TFS for GIT. Something so simple !

xstepl@gmail.com (JIRA)

unread,
Dec 4, 2015, 8:40:02 AM12/4/15
to jenkinsc...@googlegroups.com

olivida@microsoft.com (JIRA)

unread,
Feb 1, 2016, 9:40:03 PM2/1/16
to jenkinsc...@googlegroups.com

jhoppe@gmail.com (JIRA)

unread,
Apr 7, 2016, 2:27:01 PM4/7/16
to jenkinsc...@googlegroups.com
Joseph Hoppe commented on Bug JENKINS-31875
 
Re: No working folder mapping when accessing TFS (win 10)

Recreating the same job resolved this issue for me

apgray@java.net (JIRA)

unread,
May 19, 2016, 1:37:01 AM5/19/16
to jenkinsc...@googlegroups.com
apgray commented on Bug JENKINS-31875

This issue occurred for me after I moved the job to another Folder (CloudBees Folders plugin).

Wiping out the workspace did not resolve it.

Turning Use Update checkbox off did.

RayHallquist@HotMail.com (JIRA)

unread,
Aug 13, 2016, 8:46:02 AM8/13/16
to jenkinsc...@googlegroups.com

Turning Use Update resolved the issue for me.
I have spaces in the Workspace path.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

RayHallquist@HotMail.com (JIRA)

unread,
Aug 13, 2016, 8:46:02 AM8/13/16
to jenkinsc...@googlegroups.com
Ray Hallquist edited a comment on Bug JENKINS-31875
Turning Use Update off resolved the issue for me.

I have spaces in the Workspace path.

olivier.dagenais@gmail.com (JIRA)

unread,
Feb 20, 2017, 3:46:24 PM2/20/17
to jenkinsc...@googlegroups.com
Olivier Dagenais assigned an issue to David Staheli
 
Change By: Olivier Dagenais
Assignee: Olivier Dagenais David Staheli

brenton@letrabb.com (JIRA)

unread,
Jul 24, 2018, 2:04:03 PM7/24/18
to jenkinsc...@googlegroups.com
Brantone commented on Bug JENKINS-31875
 
Re: No working folder mapping when accessing TFS (win 10)

Tried all options listed here and no luck.

I'm wondering how many people had concurrent builds occurring on same slave agent? So far that's really consistent behaviour I've seen and suspecting that it's because there's contention over VersionControl.config on the agent.

Steps like updating checkboxes or the workspace name could just be that it's providing enough of a gap to to allow concurrent builds to occur??

Either way, still get this randomly  

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
Reply all
Reply to author
Forward
0 new messages