When comparing GoCD vs Rancher, the Slant community recommends Rancher for most people. In the question“What are the best Continuous Integration services with Docker support?” Rancher is ranked 11th while GoCD is ranked 13th. The most important reason people chose Rancher is:
Intuitive and easy to use web gui.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Native support for pipelines
GoCD supports pipelines natively. This way you can build your projects by pipelining them.
Pro Good traceability of what contributed to a given artifact
GoCD's LEAN value stream UI helps all stakeholders focus on efficient product delivery (instead of collections of technical tasks).
Pro Web GUI cluster management
Intuitive and easy to use web gui.
Pro Mult-environment cluster system
- Cattle (Rancher default)
- Swarm
- Kubernetes
- Mesos
Pro Service catalog is easy
Rancher provides a catalog of application templates that make it easy to deploy complex stacks.
- Rancher certified catalog
- Community service catalog
Pro Self-service application stack for self-monitoring
Great contributions from the co community who build the service stack catalog.
One of them is the "Prometheus" template which deploys a collection of containers for monitoring a platform. It's capable of querying all aspects of your environment with some nice pre-built dashboards.
Pro Access control polices
Detailed role-based access control policies can be defined independently for each cluster.
Cons
Con Need Scripts for everything
Almost all operations are shell based, they are not configurations possible, your CI is as good as your scripting
Con Does not offer many plugins
Since it's relatively new and not very popular, there are few plugins available in GoCD.