New to GO and am reading thru the on-line docs. The better use of GO Enterprise seems to be Not to run an agent that builds,tests, and deploys on the Same server where GO Enterprise is installed but instead, to use the server as a centralized build and test manager who invokes remote agents who do the heavy lifting.
Is this proper thinking?
I realize the " it depends" aspect but lets say for a software shop that has many dozen developers, located in different parts of the world and several dozen active software applications each with the normal SDLC cycles.
Thanks in advance :-)
New to GO Enterprise
Comments
2 comments
Greg
I would definitely agree with your thinking, especially as Go's standard installation is one Agent per server the concept is for the remote agents to get the artifacts from the central repository and carry out the deployment themselves. This way 4 web and 4 app servers can all get updated in less than 20 seconds. We use the go server agent to build software, another agent to run tests and then individual server agents to deploy. Some tasks that take a while like refreshing databases, have multiple agents to cover the workload
You have been a big help. Thanks Ian
Please sign in to leave a comment.