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 …
Overview
What is GoCD?
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
Recent Reviews
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…
Product Details
- About
- Tech Details
What is GoCD?
GoCD Video
GoCD Fundamental Concepts
GoCD Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(6)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
GoCD has proven to be a versatile and efficient tool for various use cases based on user experiences. Users have been able to perform staged deployments and nightly builds on multiple environments, allowing for smooth integration with third-party tools. The software's easy configuration for new pipelines has been highly appreciated, enabling users to quickly adapt and integrate it into their existing workflows. Additionally, GoCD has improved the build process by enabling parallel builds and better organization of the build flow, resulting in faster deployment times and simplified management of multiple services in microservice architectures. Users have also praised GoCD's manual deployment stages and gatekeeping feature, which has proven to be highly efficient. The software has been valuable for maintaining complex Java application deployments involving multiple servers. Moreover, some users have found GoCD to be a reliable and reproducible build automation tool. With its clear UI and conceptualization, GoCD has made knowledge transition and application deployment easier for users. Overall, GoCD has been utilized as the backbone of CI/CD systems in various organizations, facilitating continuous delivery and one-step deployments while being tightly integrated with SCM systems, binary repositories, and both on-premise and cloud infrastructure. The automation capabilities of GoCD have also been highly praised, allowing for fully automated CI/CD pipelines that enable frequent and quick releases.
User-Friendly Web Interface: Users have consistently found the web interface of GoCD to be user-friendly and visually appealing. They appreciate how easy it is to navigate and interact with the platform.
Integration with GitHub and Easy Management of Groups and Permissions: Many users liked the feature of being able to connect with GitHub using addons, as well as the ability to easily manage groups and permissions within GoCD. This functionality streamlines workflow processes.
Effective Use of Templates for Different Pipelines: After understanding how to utilize them effectively, many users have appreciated the ability to use templates for different pipelines in GoCD. This feature allows for consistent and efficient pipeline creation, saving time and effort.
Complex User Interface: Several users have found the user interface of GoCD to be complex, especially for beginners. Some reviewers have mentioned that tutorials were hard to find and that the configuration process was difficult to understand.
Limited Plugin Support: A number of users have expressed dissatisfaction with the limited plugin support in GoCD compared to competitors like Jenkins. They feel that GoCD has fewer plugins available, making it less powerful in terms of functionality and customization options.
Challenging Configuration Management: Many reviewers have found the configuration management in GoCD to be tricky and cumbersome. They desire a simpler text-based configuration format and struggle with understanding how to structure pipeline dependencies and environment correctly.
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!
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.
- 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.
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
- 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.