Skip to main content
TrustRadius
GoCD

GoCD

Overview

What is GoCD?

GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.

Read more
Recent Reviews

TrustRadius Insights

GoCD has proven to be a versatile and efficient tool for various use cases based on user experiences. Users have been able to perform …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is GoCD?

GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

4 people also want pricing

Alternatives Pricing

What is Liquibase?

Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database…

What is Bitrise?

Bitrise, software from the company of the same name in Budapest, helps users automate daily app development tasks from building through testing to deployment. With Bitrise, users can configure these tasks with a visual Workflow editor, with over 330 service integrations ready to roll. All…

Return to navigation

Product Details

What is GoCD?

GoCD Video

GoCD Fundamental Concepts

GoCD Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(6)
Loading...

Reviews

(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
August 12, 2021

CI/CD is the way!

Tung Vu | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
GoCD is used throughout the whole global AdNovum group. It's the backbone of our CI/CD system. GoCD is tightly integrated into our SCM system, our binary repo system, as well as both our internal on-premise VMs and our Azure subscription. So our engineers make changes to the code, create a PR to trigger a PR build to verify the changes. After merging to main branch, as well as on a daily basis, we have pipelines to build the main branch then push the daily artifacts to binary repo. Another daily pipeline then pick things up to deploy to a testing environment. Promotion from daily environment to other ones are triggered as needed. Everything automated!
  • 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.
  • I miss the ability to have custom build parameters on GUI. So, all the changes even the smallest ones have to be checked into SCM.
  • If there's an ability to define the priority of the pipelines, that would be great. Some build environments only have a couple of agents, so there are times that builds have to wait for quite a long time.
  • I wish that I can create a new view for a group. Currently, if I have a view for group A, then more pipelines are added to that group, I have to edit the view to manually add the new pipelines.
GoCD is easy to set up. So if you just want to get some pipelines up & running quickly, & they're quite stable, or you can have many pipelines for different needs then GoCD is great. Still, if you only want to have a few pipelines, but with the flexibility to run them with different parameters dynamically, then Jenkins is better.
  • Pipeline-as-Code
  • Automatic triggers
  • Clean & clear GUI
  • Automated CI/CD improves quality tremendously
  • People can spend time on more interesting activities instead of repeated tasks
  • Peace-of-mind when the changes are well-tested multiple times
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.
Dicky Leonardo | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
GoCD is being used for setting up a deployment pipeline for our dev environment and also when the application is ready to be deployed to production. It has built-in support for setting up the environment, different environment variables for each step and also it supports both Linux and Windows build agent.
  • Easy Setup for deployment pipeline
  • Environment Variables for each step
  • Supports both Windows and Linux agent
  • Highly customizable
  • UI can be improved
  • Location for settings can be re-arranged
  • API for setting up pipeline
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.
  • 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
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 environment makes sense but can often confuse the user while GoCD simply has a drop-down to select your environment.
Return to navigation