Go.CD vs Jenkins

Overview

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

GoCD

Stacks205

Followers325

Votes207

GitHub Stars7.3K

Forks980

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.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Jenkins, GoCD

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k

Comments

Engineering Team Lead at DCMN GmbH

Oct 22, 2021

Decided

Github Actions allowed us to drop previous CI/CD technologies like Jenkins or AWS CodeBuild. The main advantages for us are:

The Infrastructure-as-Code approach of Github Actions enables us to keep CI/CD configurations next to the code.
Github as a single platform for repositories and CI/CD simplifies our stack and effort to manage it on the daily basis.

TVcloud Team <3 Github Actions

72.2k views72.2k

Comments

Pedro Gil

Head of Engineering at lengoo GmbH

May 4, 2021

Decided

We replaced Jenkins with Github Actions for all our repositories hosted on Github. GA has two significant benefits for us compared to an external build tool: it's simpler, and it sits at eye level.

Its simplicity and smooth user experience makes it easier for all developers to adopt, giving them more autonomy.

Sitting at eye level means it's completely run and configured right alongside the code, so that it's easier to observe and adjust our builds as we go.

These two benefits have made "the build" less of a system engineer responsibility and more of a developer tool, giving developers more ownership from code to release.

77.7k views77.7k

Comments

Detailed Comparison

Jenkins	GoCD
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.	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.
Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support	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; Manual triggers allow deployment any version at anytime. And it's securable and auditable; Run tests written in most languages or frameworks, provides informative testing report; Compare both files and commit messages across any two arbitrary builds; Eliminate Bottlenecks by providing trivial parallel execution across pipelines, platforms, versions, branches, etc.; Easily reuse pipeline configurations via template system.
Statistics
GitHub Stars 24.6K	GitHub Stars 7.3K
GitHub Forks 9.2K	GitHub Forks 980
Stacks 59.2K	Stacks 205
Followers 50.4K	Followers 325
Votes 2.2K	Votes 207
Pros & Cons
Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Limited abilities with declarative pipelines 7 Lack of support	Pros 32 Open source 27 Pipeline dependencies 25 Pipeline structures 22 Can run jobs in parallel 20 Very flexible Cons 2 Lack of plugins 2 Horrible ui 1 No support
Integrations
No integrations available	Docker Kubernetes Slack

What are some alternatives to Jenkins, GoCD?

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Appveyor

AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.

Related Comparisons

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 vs Jenkins