GoCD vs Jenkins

Overview

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

GoCD

Stacks205

Followers325

Votes207

GitHub Stars7.3K

Forks980

GoCD vs Jenkins: What are the differences?

Introduction

This Markdown code provides a comparison between GoCD and Jenkins, highlighting their key differences.

1. Architecture: GoCD has a server-agent architecture, where the server manages job distribution and agents execute the jobs. On the other hand, Jenkins follows a master-slave architecture, with one master managing job scheduling and multiple slaves executing the jobs.
2. Pipeline Configuration: In GoCD, pipeline configuration is defined using a declarative format, allowing easy visualization and understanding of the pipeline flow. In Jenkins, pipeline configuration can be done using either a scripted or declarative syntax, providing more flexibility but potentially leading to more complex configurations.
3. Plugin Ecosystem: Jenkins has a vast plugin ecosystem, offering numerous integrations with various tools and technologies. GoCD also has plugins available, but the number and variety of plugins may be more limited compared to Jenkins.
4. User Interface: GoCD provides a more modern and user-friendly web interface, allowing users to easily navigate and interact with the system. Jenkins, although highly customizable, may require additional configuration or plugins to achieve a similar level of user interface experience.
5. Pipeline Visualization: GoCD provides powerful built-in tools for visualizing pipeline status, showing the flow of control and highlighting any issues or bottlenecks. Jenkins, while also offering plugins for visualization, may require additional setup and customization to achieve a similar level of visibility.
6. Learning Curve: GoCD has a steeper learning curve compared to Jenkins, especially for users who are already familiar with Jenkins. This is due to the differences in architecture, pipeline configuration, and user interface.

In Summary, GoCD and Jenkins differ in their architecture, pipeline configuration, plugin ecosystem, user interface, pipeline visualization, and learning curve.

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

StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k

Comments

Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k

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

Bitbucket vs GitHub vs GitLab

AWS CodeCommit vs Bitbucket vs GitHub

Docker Swarm vs Kubernetes vs Rancher

Grunt vs Webpack vs gulp

Grafana vs Graphite vs Kibana

GoCD vs Jenkins: What are the differences?

Introduction

This Markdown code provides a comparison between GoCD and Jenkins, highlighting their key differences.

1. Architecture: GoCD has a server-agent architecture, where the server manages job distribution and agents execute the jobs. On the other hand, Jenkins follows a master-slave architecture, with one master managing job scheduling and multiple slaves executing the jobs.
2. Pipeline Configuration: In GoCD, pipeline configuration is defined using a declarative format, allowing easy visualization and understanding of the pipeline flow. In Jenkins, pipeline configuration can be done using either a scripted or declarative syntax, providing more flexibility but potentially leading to more complex configurations.
3. Plugin Ecosystem: Jenkins has a vast plugin ecosystem, offering numerous integrations with various tools and technologies. GoCD also has plugins available, but the number and variety of plugins may be more limited compared to Jenkins.
4. User Interface: GoCD provides a more modern and user-friendly web interface, allowing users to easily navigate and interact with the system. Jenkins, although highly customizable, may require additional configuration or plugins to achieve a similar level of user interface experience.
5. Pipeline Visualization: GoCD provides powerful built-in tools for visualizing pipeline status, showing the flow of control and highlighting any issues or bottlenecks. Jenkins, while also offering plugins for visualization, may require additional setup and customization to achieve a similar level of visibility.
6. Learning Curve: GoCD has a steeper learning curve compared to Jenkins, especially for users who are already familiar with Jenkins. This is due to the differences in architecture, pipeline configuration, and user interface.

In Summary, GoCD and Jenkins differ in their architecture, pipeline configuration, plugin ecosystem, user interface, pipeline visualization, and learning curve.