How might the authorizationToken affect template build agents?

Hi everyone

I'm setting up a virtualised build lab at work, or, to use the term du jour, a build cloud.  This is very similar to the EC2 feature TeamCity ships with, but runs locally instead of on Amazon's infrastructure.  

I have my build agent all completely configured with all the build requirements, dependencies, etc.  What's confusing me a little bit is the authorizationToken configuration setting.  Does this need to be unique per build agent?  I noticed from earlier experiments that it is a required configuration setting in order for the agent to communicate with the server.  Or can I clone multiple times a VM template with the authorizationToken specified without any issues?

Thanks in advance


Please sign in to leave a comment.