You shouldn't require "Administer build permissions" to Clone a Build - by David Crookes

Status : 

 


2
0
Sign in
to vote
ID 785958 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 4/30/2013 1:46:16 PM
Access Restriction Public

Description

You cannot clone a build unless you have the permission "Administer build permissions" which is described as "Users who have this permission can administer the build permissions for other users.".

You shouldn't have to to grant this permission to allow a build to be cloned as you are providing to much privilege.  I'd expect this to action to be linked to to "Edit Build Definition"
Sign in to post a comment.
Posted by Justin [MSFT] on 5/6/2013 at 6:24 AM
Clone Build Definition is a powertool, not part of the core VS product. It hits this error because it is trying to replicate the security settings of the original build definition onto the new one. It should be a warning rather than an error since, as you pointed out, the operation basically works without it.

Transferring this bug to the powertool team.
Posted by Microsoft on 5/2/2013 at 1:50 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by David Crookes on 5/1/2013 at 4:22 AM
Further to this I can confirm that after the error is displayed the build does actually get cloned.

The last test on this was using VS2012 version 11.0.60315.01 Update 2
Posted by Macy [MSFT] on 4/30/2013 at 1:53 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)