I have over 300 instances that would need deployment from GoCD. I looked over the GoCD agent and how it works, and see that it takes 500M and polls the server every few seconds. The documentation did mention the server will need to be scaled up as the number of agents and pipelines increase.
>From a resource utilization perspective, for deployments, which would work better? 1 - Install GoCD agent on every server that needs deployment. The environment would be named according to the type of deployment required. EG 'test myproject', 'prod thisproject', etc. 2 - Treat goCD agents as independent workers and give them something like ansible and the ability to get into each server that would have been covered by agents running in 'test myproject' environment >From a documentation perspective putting a gocd agent on each target server would make the target instances easily visible in GoCD, right? Would there be a way to make it easily visible in GoCD where (what exact instances) a deployment is going? -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/6079a26c-f44b-45ac-8233-9a64a63723a8n%40googlegroups.com.
