Need advice about which tool to choose?Ask the StackShare community!
Go.CD vs Puppet Labs: What are the differences?
Developers describe Go.CD as "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. On the other hand, Puppet Labs is detailed as "Server automation framework and application". Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
Go.CD belongs to "Continuous Integration" category of the tech stack, while Puppet Labs can be primarily classified under "Server Configuration and Automation".
Some of the features offered by Go.CD are:
- 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
On the other hand, Puppet Labs provides the following key features:
- Insight- Puppet Enterprise's event inspector gives immediate and actionable insight into your environment, showing you what changed, where and how by classes, nodes and resources.
- Discovery- Puppet Enterprise delivers a dynamic and fully-pluggable discovery service that allows you to take advantage of any data source or real-time query results to quickly locate, identify and group cloud nodes.
- Provisioning- Automatically provision and configure bare metal, virtual, and private or public cloud capacity, all from a single pane. Save time getting your cloud projects off the ground by reusing the same configuration modules you set up for your physical deployments.
"Open source" is the top reason why over 29 developers like Go.CD, while over 45 developers mention "Devops" as the leading cause for choosing Puppet Labs.
Go.CD and Puppet Labs are both open source tools. Puppet Labs with 5.37K GitHub stars and 2.1K forks on GitHub appears to be more popular than Go.CD with 5.02K GitHub stars and 791 GitHub forks.
Uber Technologies, Twitch, and PayPal are some of the popular companies that use Puppet Labs, whereas Go.CD is used by Auto Trader, Hazeorid, and OpenX. Puppet Labs has a broader approval, being mentioned in 180 company stacks & 49 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 GoCD
- Open source32
- 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
Pros of Puppet Labs
- Devops52
- Automate it44
- Reusable components26
- Dynamic and idempotent server configuration21
- Great community18
- Very scalable12
- Cloud management12
- Easy to maintain10
- Free tier9
- Works with Amazon EC26
- Declarative4
- Ruby4
- Works with Azure3
- Works with OpenStack3
- Nginx2
- Ease of use1
Sign up to add or upvote prosMake informed product decisions
Cons of GoCD
- Lack of plugins2
- Horrible ui2
- No support1
Cons of Puppet Labs
- Steep learning curve3
- Customs types idempotence1
Sign up to add or upvote consMake informed product decisions
What is GoCD?
What is Puppet Labs?
Need advice about which tool to choose?Ask the StackShare community!
What companies use GoCD?
What companies use Puppet Labs?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with GoCD?
What tools integrate with Puppet Labs?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+42
+42