[英]TFS Release Management vNext ReleaseManagementShare
I am trying to deploy a sample project with tfs release management vNext. 我正在尝试使用tfs版本管理vNext部署示例项目。 I tried a lot of things (for example: VS RM – vNext Template for On-Premise Target Server in Un-trusted Domain - although I am in a trusted domain) but am now totally lost. 我尝试了很多事情(例如: VS RM –用于不受信任域中的本地目标服务器的vNext模板 -尽管我位于受信任域中),但现在完全迷失了。 My vNext deployment tells me: 我的vNext部署告诉我:
ROBOCOPY - ERROR 3 (0x00000003) Accessing Source Directory \\rmServer\\ReleaseManagementShare\\15b27b05-d176-492d-b534-268af1845a36\\2\\ComponentName\\ The system cannot find the path specified. ROBOCOPY-错误3(0x00000003)访问源目录\\ rmServer \\ ReleaseManagementShare \\ 15b27b05-d176-492d-b534-268af1845a36 \\ 2 \\ ComponentName \\系统找不到指定的路径。
And this is true. 这是真的。 The folder with the id does not exist. ID为的文件夹不存在。
Concrete questions: 具体问题:
Can somebody help out? 有人可以帮忙吗?
The ReleaseManagementShare
folder is generally created by the installer when you set up the RM server -- or at least I recently observed that behavior in RM 2015 Update 1, I'm not sure if older versions did that. ReleaseManagementShare
文件夹通常由安装程序在设置RM服务器时创建-或至少我最近观察到RM 2015 Update 1中的行为,我不确定较旧的版本是否这样做。 If it doesn't exist, you can create it yourself. 如果不存在,则可以自己创建。 Make sure your RM Server service account has read/write access to it. 确保您的RM Server服务帐户对其具有读/写访问权限。 This folder typically isn't used. 通常不使用此文件夹。
The ReleaseManagementShare
folder is only used if you're using a XAML build and have the build output set to go to Server
instead of a file share. 仅当您使用XAML构建并将构建输出设置为转到Server
而不是文件共享时,才使用ReleaseManagementShare
文件夹。 It may be used for the new build system as well when you choose to store your artifacts on the server, but I haven't tested that scenario. 当您选择将工件存储在服务器上时,它也可以用于新的构建系统,但是我还没有测试这种情况。 If you push your binaries to a file share, this folder is completely irrelevant. 如果将二进制文件推送到文件共享,则此文件夹完全不相关。 See this for more details: https://blogs.msdn.microsoft.com/visualstudioalm/2014/11/11/whats-new-in-release-management-for-vs-2013-update-4/ 请参阅此以获取更多详细信息: https : //blogs.msdn.microsoft.com/visualstudioalm/2014/11/11/whats-new-in-release-management-for-vs-2013-update-4/
Basically, there are two potential UNC shares involved: 基本上,涉及到UNC的两个潜在份额:
ReleaseManagementShare
. 另一个是此ReleaseManagementShare
。 It comes into play when you don't have the share outlined in #1, and instead are storing your binaries in TFS. 当您没有在#1中概述共享时,它将起作用,而是将二进制文件存储在TFS中。 The targets servers still need to get the binaries somehow, so the release management server will "stage" them in the ReleaseManagementShare
so the target machines can grab them via the same mechanism they would use to grab them from the build artifact share. 目标服务器仍然需要以某种方式获取二进制文件,因此发行版管理服务器会将它们“ ReleaseManagementShare
”在ReleaseManagementShare
以便目标计算机可以通过与从构建工件共享中获取二进制文件所使用的相同机制来对其进行捕获。 The ID is just a random GUID. 该ID只是一个随机GUID。
I'm assuming you're using the new build system since you're asking about artifacts. 我假设您正在使用新的构建系统,因为您正在询问工件。 For the Artifact Type, I know for a fact that File Share works. 对于工件类型,我知道文件共享有效。 I'm not 100% certain that Server works, however. 但是,我不确定100%是否可以使用Server。
The artifact name can be anything you want, but it's important to note that the component name that you define in RM server must match the artifact name , otherwise it will fail to find the binaries. 工件名称可以是您想要的任何名称,但请务必注意,您在RM服务器中定义的组件名称必须与工件名称匹配 ,否则它将无法找到二进制文件。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.