Need advice about which tool to choose?Ask the StackShare community!
Ansible vs Go.CD: What are the differences?
What is Ansible? Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine. Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
What is Go.CD? Open source continuous delivery tool allows for advanced workflow modeling and dependencies management. GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.
Ansible belongs to "Server Configuration and Automation" category of the tech stack, while Go.CD can be primarily classified under "Continuous Integration".
Some of the features offered by Ansible are:
- Ansible's natural automation language allows sysadmins, developers, and IT managers to complete automation projects in hours, not weeks.
- Ansible uses SSH by default instead of requiring agents everywhere. Avoid extra open ports, improve security, eliminate "managing the management", and reclaim CPU cycles.
- Ansible automates app deployment, configuration management, workflow orchestration, and even cloud provisioning all from one system.
On the other hand, Go.CD provides the following key features:
- Model complex workflows with dependency management and parallel execution
- Easy to pass once-built binaries between stages
- Visibility into your end-to-end workflow. Track a change from commit to deploy at a glance
"Agentless" is the top reason why over 251 developers like Ansible, while over 29 developers mention "Open source" as the leading cause for choosing Go.CD.
Ansible and Go.CD are both open source tools. It seems that Ansible with 38.2K GitHub stars and 16K forks on GitHub has more adoption than Go.CD with 5.02K GitHub stars and 791 GitHub forks.
According to the StackShare community, Ansible has a broader approval, being mentioned in 960 company stacks & 587 developers stacks; compared to Go.CD, which is listed in 28 company stacks and 8 developer stacks.
I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.
Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.
I'm just getting started using Vagrant to help automate setting up local VMs to set up a Kubernetes cluster (development and experimentation only). (Yes, I do know about minikube)
I'm looking for a tool to help install software packages, setup users, etc..., on these VMs. I'm also fairly new to Ansible, Chef, and Puppet. What's a good one to start with to learn? I might decide to try all 3 at some point for my own curiosity.
The most important factors for me are simplicity, ease of use, shortest learning curve.
I have been working with Puppet and Ansible. The reason why I prefer ansible is the distribution of it. Ansible is more lightweight and therefore more popular. This leads to situations, where you can get fully packaged applications for ansible (e.g. confluent) supported by the vendor, but only incomplete packages for Puppet.
The only advantage I would see with Puppet if someone wants to use Foreman. This is still better supported with Puppet.
If you are just starting out, might as well learn Kubernetes There's a lot of tools that come with Kube that make it easier to use and most importantly: you become cloud-agnostic. We use Ansible because it's a lot simpler than Chef or Puppet and if you use Docker Compose for your deployments you can re-use them with Kubernetes later when you migrate
Pros of Ansible
- Agentless283
- Great configuration209
- Simple198
- Powerful176
- Easy to learn154
- Flexible68
- Doesn't get in the way of getting s--- done55
- Makes sense35
- Super efficient and flexible30
- Powerful27
- Dynamic Inventory11
- Backed by Red Hat9
- Works with AWS7
- Cloud Oriented6
- Easy to maintain6
- Multi language4
- Because SSH4
- Vagrant provisioner4
- Easy4
- Simple4
- Procedural or declarative, or both4
- Simple and powerful4
- Consistency3
- Merge hash to get final configuration similar to hiera2
- Debugging is simple2
- Fast as hell2
- Well-documented2
- Masterless2
- Manage any OS1
- Certified Content1
- Work on windows, but difficult to manage1
Pros of GoCD
- Open source31
- Pipeline dependencies27
- Pipeline structures25
- Can run jobs in parallel22
- Very flexible20
- Plugin architecture15
- Environments can keep config secure13
- Great UI12
- Good user roles and permissions10
- Supports many material dependencies9
- Fan-in, Fan-out7
- Designed for cd not just ci6
- Empowers product people to make delivery decisions4
- Flexible & easy deployment2
- Pass around artifacts2
- Build once1
Sign up to add or upvote prosMake informed product decisions
Cons of Ansible
- Dangerous8
- Hard to install5
- Doesn't Run on Windows3
- Bloated3
- Backward compatibility3
- No immutable infrastructure2
Cons of GoCD
- Lack of plugins2
- Horrible ui2
- No support1
Sign up to add or upvote consMake informed product decisions
What is Ansible?
What is GoCD?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Ansible?
What companies use GoCD?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Ansible?
What tools integrate with GoCD?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+14
+13
+30
+33
+23+42+37+26