We changed our name from IT Central Station: Here's why

GoCD OverviewUNIXBusinessApplication

GoCD is #6 ranked solution in top Release Automation tools, #7 ranked solution in top Build Automation tools, and #13 ranked solution in top Application Lifecycle Management Suites. PeerSpot users give GoCD an average rating of 8 out of 10. GoCD is most commonly compared to GitLab: GoCD vs GitLab. The top industry researching this solution are professionals from a computer software company, accounting for 32% of all views.
What is GoCD?
GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers businesses a first-class build and deployment engine for complete control and visibility. It was designed for continuous delivery and the concepts essential to this practice are built in at the core.

GoCD was previously known as Adaptive ALM, Thoughtworks Go.

Buyer's Guide

Download the Application Lifecycle Management (ALM) Suites Buyer's Guide including reviews and more. Updated: January 2022

GoCD Customers
Ancestry.com, Barclay Card, AutoTrader, BT Financial Group, Gamesys, Nike, Vodafone, Haufe Lexware, Medidata, Hoovers
GoCD Video

GoCD Pricing Advice

What users are saying about GoCD pricing:
"It's an open-source and free tool."

GoCD Reviews

Filter by:
Filter Reviews
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Showingreviews based on the current filters. Reset all filters
Dmytro Kutetskyi
Solution Architect | Head of BizDev at Greg Solutions
Real User
Top 5Leaderboard
User-friendly interface, good integration with LDAP, and has an easily-extendable open architecture
Pros and Cons
  • "Permission separations mean that we can grant limited permissions for each team or team member."
  • "The documentation really should be improved by including real examples and more setup cases."

What is our primary use case?

We are using GoCD as our main tool for Continuous Delivery (CD) pipelines. We integrated GoCD with Continuous Delivery tools, such as Jenkins, TeamCity, etc.

We actively using the following features of the GoCD: LDAP integration, server-agents architecture (run GoCD agents on-demand in a Kubernetes cluster or on AWS EC2 instances to keep the operations cost low), plug-in architectures, Infrastructure as a code (pipelines in GoCD could be described in code repository).

Besides all these features, GoCD has a great UI with flexible permissions management.

How has it helped my organization?

GoCD provides a good UI for development, QA, release, and management teams to be able to deliver new application versions in a transparent and predictable way.

We can setup GoCD to split the permissions between teams: the DEV environment is automatically updated, only the QA team could deploy the new version to the TEST environment, and only the management/release team can deploy new versions to the sensitive environment, such as UAT/DEMO/PROD.

We wrote the custom integration of the GoCD with TeamCity and Jenkins using the GoCD API and pipelines configuration files.

What is most valuable?

  1. It has a user-friendly interface, which for free and open-source tools, the UI is really amazing and simple. It takes a few minutes to show the CD process to new users and onboard them.
  2. Permission separations mean that we can grant limited permissions for each team or team member.
  3. Integration with LDAP allows us to use central user management and leverage permission separation inside GoC.
  4. Plug-in architecture gives us the ability to easily extend GoCD, although it is not always possible because of the limited number of plugins.
  5. As an open-source solution, we always can check the issues, or rely on community support.

What needs improvement?

  1. If the workflows were updated for any reason, such as when environments are created, deleted, or changed, the previous delivery pipelines will be broken. You can't redeploy the old version or propagate new versions to the following environments.
  2. It would be great to have more flexibility in configuring the initial job. We are using GoCD for the CD process only, so any jobs are triggered by external CI tools, not the GoCD itself. We don't need to configure code repositories or other inputs that GoCD is expecting, so we are forced to create the dummy repository, and the commit history is not relevant to the CD process.
  3. It would be great to have more available plug-ins to cover more functionality inside GoCD.
  4. The documentation really should be improved by including real examples and more setup cases.

For how long have I used the solution?

We have been using GoCD for between four and five years.

What do I think about the scalability of the solution?

It's pretty scalable and you can run few deployments in parallel, depending on the number of available agents. You can scale manually or automatically.

Which solution did I use previously and why did I switch?

We considered using Jenkins with custom plug-ins and TeamCity, but decided to use GoCD because it provides a better UX for CD.

I would advise using Azure DevOps if you are locked on Azure. Also, take a look at CircleCI, cloud GitLab CI, and BitBucket pipelines if you need a paid/all-in-one CI/CD solution. These tools also offer free and limited editions.

If you are interested in the features and an open-source solution, you can take a look at ConcourseCI or ArgoCD.

What's my experience with pricing, setup cost, and licensing?

It's an open-source and free tool.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.