更新构建保留策略设置的权限 [英] Permissions for updating build retention policy settings
问题描述
在TFS 2015 Update 3中更新项目集合级别的构建设置需要哪些权限？ 它们已由非项目收集管理员的人更新。
What permissions are required for updating the build settings at the project collection level in TFS 2015 Update 3? They have been updated by someone who is not a project collection administrator.
这是针对此URL的最大保留策略，默认保留策略和永久销毁构建设置：
This is for the Maximum Retention Policy, Default Retention Policy and Permanently Destroy Builds settings at this URL:
http：// [tfsserver]：8080 / tfs / [collection] / _admin / _buildQueue
http://[tfsserver]:8080/tfs/[collection]/_admin/_buildQueue
推荐答案
您好IKdevrie，
Hi IKdevrie,
感谢您发布此处。
用户基本和高级访问级别具有编辑保留策略的权限。并且具有"编辑构建定义"的用户在所有构建定义中都可以编辑构建定义中的保留策略。如果这些用户（具有编辑集合级别的权限
保留策略但在项目级别没有"编辑构建定义"）更新集合级别保留策略，所有未添加的定义额外保留策略将受集合
级别保留策略的影响。因此，作为一种变通方法，您可以向构建定义添加额外的保留策略，并且构建不会受这些用户设置的最大保留策略的影响。您也可以将您的uservoice提交到以下链接，TFS产品
团队正在那里听你的声音：
The users Basic and Advanced access level have permission to edit the retain policy. And the users who have "edit build definitions" in all build definitions could edit the retain policy in build definition. If these users (who have permission to edit the collection level retain policy but not have the "edit build definitions" in the project level) update the collection level retain policy, all the definitions which are not been added extra retain policy will be affected by the collection level retain policy. So as a workaround, you could add extra retain policy to the build definition, and the build will not be affected by the Maximum Retain policy set by these users. Also you could submit your uservoice to the following link, TFS Product Team is listening to your voice there:
https://visualstudio.uservoice.com/forums/330519-team-services
最诚挚的问候
Limitxiao Gao
这篇关于更新构建保留策略设置的权限的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
