Go.CD vs Jenkins: What are the differences?
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; Jenkins: An extendable open source continuous integration server. In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Go.CD and Jenkins can be primarily classified as "Continuous Integration" tools.
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, Jenkins provides the following key features:
- Easy installation
- Easy configuration
- Change set support
"Open source" is the top reason why over 29 developers like Go.CD, while over 497 developers mention "Hosted internally" as the leading cause for choosing Jenkins.
Go.CD and Jenkins are both open source tools. Jenkins with 13.2K GitHub stars and 5.43K forks on GitHub appears to be more popular than Go.CD with 4.98K GitHub stars and 789 GitHub forks.
According to the StackShare community, Jenkins has a broader approval, being mentioned in 1753 company stacks & 1479 developers stacks; compared to Go.CD, which is listed in 27 company stacks and 6 developer stacks.
What is Go.CD?
What is Jenkins?
Want advice about which of these to choose?Ask the StackShare community!
What tools integrate with Go.CD?
What tools integrate with Jenkins?
All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.
Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.
- Continuous Deploy
- Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
- Staging and production stages: Build and rollback quicly with Ansistrano playbook
- Sending messages of job results to Chatwork.
Currently serves as the location that our QA team builds various automated testing jobs.
At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.