Reputation: 701
Our shop is transitioning from an TFS 2008 server to VSTS. I've been tasked with setting up a server to download and configure agents. There is a lot of MS's documentation online which I am reviewing--however, a brief practical document outlining what exactly is needed would be helpful. For example, should I create a service account for these agents to run under? If so, what sort of Windows permissions are appropriate? Can any of you direct me to such a reference guide?
Upvotes: 1
Views: 471
Reputation: 1851
Basically, VSTS provides a script to setup agents. You need to check in your agent queues, and there should be a setup script in there that you can copy/paste on your build machines.
If you're deploying release agents, they must run with a user that has enough permissions to manage a release (i.e execute sql scripts, manage IIS sites, ...). There should also be a setup script in there that you can copy/paste on your release machines.
For build agents, they can run with the default identity, as they usually do not access resources of the machines; they only need to modify their sandbox environments. However, if your builds include integration tests and other steps that are environment-bound, you should provide a custom identity that has the required permissions.
Upvotes: 1