TFS抛出映射异常 [英] TFS throws a mapping exception

查看:121
本文介绍了TFS抛出映射异常的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


我正在使用
Jenkins的TFS插件
。 在你解雇之前,如果你因为Jenkins而倾向于混合,我在这里问,因为这个插件使用Java类来访问TFS而不是TEE客户端。 我希望我假设微软会产生
这些类。


通常情况下,除了这个好奇心之外,事情都很顺利。 我有两个Linux构建代理。 有时,在另一个系统构建完成后,我会在其中一个系统上构建此异常:


FATAL:com.microsoft.tfs.core.clients.versioncontrol。 exceptions.MappingConflictException:路径/ home / builder / jenkins / workspace / LinuxBuildCompileOnly已映射到工作空间Hudson-LinuxBuildCompileOnly-devlnx64-04。


这发生在主机devlnx64- 03. 造成这种情况的原因是什么? 对日志的审查显示以下内容:
$


从计算机'devlnx64-03'中删除名为'Hudson-LinuxBuildCompileOnly-devlnx64-03'的工作空间...

删除了名为"Hudson-LinuxBuildCompileOnly-devlnx64-03"的1个工作区。

创建工作区' Hudson-LinuxBuildCompileOnly-devlnx64-03'由'WINNTDOM\umtfsservice'拥有......

创建工作区'Hudson-LinuxBuildCompileOnly-devlnx64-03'。

将'$ / Project / Main'映射到本地文件夹'/ home / builder / jenkins / workspace / LinuxBuildCompileOnly'in

 工作空间'Hudson-LinuxBuildCompileOnly-devlnx64-03'...



$
该流程删除旧工作区和重拍它。 为什么TFS抱怨这种映射? 是不是满足于允许将TFS位置映射到不同系统和不同工作区中的多个位置? 我对此非常好奇,并且非常感谢这里的任何见解。


如上所述,Jenkins正处于混合状态。 因此,我在他们的讨论区问过。 但是,如果Microsoft生成插件使用的Java类,我认为在这里提问也可能是谨慎的。 如果这不是正确的论坛,
请告诉我。


Andy

解决方案

嗨Andy,


>>该过程将删除旧工作区并重新创建它。 
为什么TFS会抱怨这种映射?


我不认为这是TFS行动,只是Jenkins的TFS插件的动作。


另一方面,Jenkins的TFS插件是第三方插件,我们不知道它是如何构建的,这里不支持它。我认为它可以使用TFS SDK for JAVA来构建它。如果您有JFSA的TFS SDK问题(在您自己的应用程序中使用
构建应用程序),我们可以为您提供建议。


因此,我建议您将此问题发布到其网站/论坛进行处理。


问候


Starain


Hi,

I'm using the TFS plugin for Jenkins.  Before you dismiss this, if you're inclined to because of Jenkins in the mix, I'm asking here because this plugin uses Java classes for accessing TFS rather than the TEE client.  I hope my assumption that Microsoft produces these classes is the case.

Usually, things work well except for this one curiosity.  I have two Linux build agents.  Occasionally, I get this exception when building on one of these systems after the build was done on the other:

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.

As mentioned, Jenkins is in the mix.  As such, I've asked on their discussion board.  However, if Microsoft produces the Java classes in use by the plugin, I thought it might be prudent to ask here as well.  If this isn't the correct forum, please let me know.

Andy

解决方案

Hi Andy,

>> The process removes the old workspace and remakes it.  Why is TFS complaining about this mapping?

I don’t think it is TFS action, just the actions of TFS plugin for Jenkins.

On the other hand, the TFS plugin for Jenkins is the third-party plugin, which we don’t know how it build and it isn’t supported here. I think it may use TFS SDK for JAVA to build it. If you have issue of TFS SDK for JAVA (build app with it in your own application), we could give you suggestions.

So, I suggest that you should post this issue to its site/forum to deal with it.

Regards

Starain


这篇关于TFS抛出映射异常的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆