为什么所有拉动的源文件都是ReadOnly？ [英] Why all pulled source files are ReadOnly?

问题描述

我通过  vsts-agent-win7-x64-2.104.2.zip安装了代理服务并配置了我的构建定义。当我运行这个构建时，它从VSO代码库中提取源文件，我注意到默认情况下源文件访问权限都是ReadOnly。由于构建的
将在构建期间更新一些源文件，因此它使构建失败，"访问被拒绝"

谁知道在同步后如何使它们可写而不是ReadOnly - 代码库？ 

谢谢，

-Frank

解决方案

你好，

感谢您在此发帖！

根据我的理解，将文件复制到构建代理可能依赖于服务器权限。

我我发现有一个讨论涉及同一个问题，请参考此链接，

https://social.msdn.microsoft.com/Forums / en-US / 887c463f-7c58-4173-a789-d5bee24df392 / winrm-a​​ccess-denied-azure-file-copy-task-in-vso-build-definition？forum = TFService 可能对您有所帮助。

如果没有帮助，请告诉我们，我们很乐意为您提供更多帮助。

问候，

Swikruti

I installed the agent service by vsts-agent-win7-x64-2.104.2.zip and configured my build definition. When I ran this build, it pulled source files from VSO code base, I notice that the source files access permission are all ReadOnly by default. due to the build will update some source files during build, so it makes the build failed, "access denied"

Who knows how to make them writable not ReadOnly after sync-ing the code base? 

Thanks,

-Frank

解决方案

Hello,

Thank you for posting here!

As per my understanding, after copying the files to build agent that might be depend upon the server permission.

I have found one discussion related the same issue, please refer this link, https://social.msdn.microsoft.com/Forums/en-US/887c463f-7c58-4173-a789-d5bee24df392/winrm-access-denied-azure-file-copy-task-in-vso-build-definition?forum=TFService which might help you.

If it doesn’t help, let us know, we are happy to assist you more.

Regards,

Swikruti

这篇关于为什么所有拉动的源文件都是ReadOnly？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！