We just raised a $30M Series A: Read our story

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. IT Central Station 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: December 2021

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

Archived GoCD Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
it_user173667
Senior Developer at a tech vendor with 201-500 employees
Vendor
We have a completely automated product delivery process but it needs better statistic and report options.‚Äč

What is most valuable?

The Pipeline concept, Fan-in Fan-out, and Compare build are the most valuable to me.

How has it helped my organization?

We used to run our complex build process on TFS build and release manager, but its complicated license issue restricted us to roll it out to every team, and we always found a limited configuration for it to work as expected. After we switched to GO, each team can set-up their own delivery pipeline and run it themselves. Now, we have a completely automated product delivery process.

What needs improvement?

GO statistic and report options.

For how long have I used the solution?

6 months.

What was my experience with deployment of the solution?

No major issues.

What do I think about the stability of the solution?

So far so good.

What do I think about the scalability of the solution?

No, we don't have any problem scaling our GO implementation from either infrastructure or team points of view.

How are customer service and technical support?

Customer Service:

Haven't had a need to call them.

Technical Support:

Good documentation but not much community support compare to other CI/ CD tools

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

I used TFS build, Jenkins and TeamCity previously. We switched to GO because the pipeline concept promoted by GO is a good match with our process.

How was the initial setup?

It's pretty easy, I got it done without any problems.

What about the implementation team?

In-house, and all our developers take part in keeping their GO server running.

What was our ROI?

GO is open source, our initial cost is zero but it comes with a bit of learning curve so if your delivery process isn't that complex, I think other tools might give you better ROI.

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

Zero initial cost, and we host them on Azure, 8-9 VMs, at approximately $14 per day.

Which other solutions did I evaluate?

Go was our winner when evaluated, along with Jenkins, TFS build, Atlassian Bamboo and Team City.

What other advice do I have?

GO doesn't come with a lot of out of the box features like other tools, don't expect that you can get it to work by clicking the NEXT button.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
ITCS user
DevOps Engineer at a healthcare company with 51-200 employees
Vendor
Valuable: hackability, visual representation of build pipelines. Room for improvement: user management, documentation

What is most valuable?

Hackability, visual representation of build pipelines, open source Apache License 2.0

How has it helped my organization?

Before implementing Go we used librarian-puppet to deploy code to different Puppet master servers. With Go we were able to automate that process, implement extra code checking functionality and get a nice visual view of our environments state.

What needs improvement?

User management, Documentation, Advanced GUI functionality.

For how long have I used the solution?

6 months

What was my experience with deployment of the solution?

Nothing which was Go's fault.

What do I think about the stability of the solution?

No stability issues.

What do I think about the scalability of the solution?

We have just one Go server and haven't looked into scalability yet.

How are customer service and technical support?

Customer Service:

We used the online community only and hence cannot comment on this.

Technical Support:

We used the online community only and hence cannot comment on this.

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

We used librarian-puppet. We switched because of greater automation, transparency and manageability of deploying our Puppet code through our environments.

How was the initial setup?

It was straightforward because there are online resources on how to do it.

What about the implementation team?

In-house team.

What was our ROI?

The product is free to use. In terms of value added it has more than achieved everything we wanted from it and more.

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

Setup cost was 1 week's time of one of our team member.

Which other solutions did I evaluate?

Jenkins.

What other advice do I have?

Try out alternatives and pick the one which fits you the best.

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