How to: Establish Permissions for Team Foundation Build Computer
Team Foundation Build uses build types to configure the conditions under which a single solution or a set of solutions in a team project will be built. In order to run a build, you will have to either create a new build type or use an existing build type that has been previously created. For more information about how to create a new build type, see.
Additionally, you must make sure that the appropriate security permissions have been established on the build computer that the build type is configured to use, and that the users who will be running the build are granted the appropriate permissions as described in the following procedure.
To perform this procedure, you must have the Team Foundation Start a build permission set to Allow. For more information, see.
To establish build permissions
Contact the system administrator for the build computer that you selected and determine the name of the account under which Team Build Service is running.
On Team menu, select Team Project Settings and then Group Membership.
The Project Groups dialog box appears.
Under the Groups, select <Team project name>\Build Service. Click Properties.
The Team Foundation Server Group Properties dialog box appears.
Click the Members tab. If the account name from step 1 is present in the member list, then the selected build computer can build this build type. Otherwise, follow these steps:
In the Add users and groups section, select Windows User or Group and then click Add.
The Select Users or Groups dialog box appears.
In Select Users or Groups dialog box, type the name of the account that is associated with the Team Build Service on the build computer used for this build type.
If this build type is built on multiple build computers, then all the Team Foundation Build Service accounts must be added as members of this project Build Services group.
You have to configure which users you want to be able to run build types. You do this by granting the Start a build permission. For more information, seeand .