GoCD

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
GoCD
Score 8.0 out of 10
N/A
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.N/A
Pricing
GoCD
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
GoCD
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup FeeNo setup fee
Additional Details—
More Pricing Information
Community Pulse
GoCD
Considered Both Products
GoCD
Chose GoCD
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to …
Chose GoCD
I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The …
Top Pros
Top Cons
Best Alternatives
GoCD
Small Businesses
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.9 out of 10
Enterprises
GitLab
GitLab
Score 8.9 out of 10
All AlternativesView all alternatives
User Ratings
GoCD
Likelihood to Recommend
9.0
(2 ratings)
User Testimonials
GoCD
Likelihood to Recommend
ThoughtWorks
Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
Read full review
Pros
ThoughtWorks
  • Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
  • The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
  • Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
Read full review
Cons
ThoughtWorks
  • UI can be improved
  • Location for settings can be re-arranged
  • API for setting up pipeline
Read full review
Alternatives Considered
ThoughtWorks
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
Read full review
Return on Investment
ThoughtWorks
  • ROI has been good since it's open source
  • Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
  • More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date
Read full review
ScreenShots