GoCD

(14)
4.0 out of 5 stars

Go's OSS distribution uses an embedded database. That's great for getting started. But, if you need to scale beyond a few teams and several pipelines, our PostgreSQL plugin gives you the performance upgrade necessary for hundreds of pipelines and agents.

Work for GoCD?

Learning about GoCD?

We can help you find the solution that fits you best.

Find the Right Product

GoCD Reviews

Ask GoCD a Question
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • User Industry
  • For Category
Ratings
Company Size
User Role
User Industry
For Category
Showing 14 GoCD reviews
LinkedIn Connections
GoCD review by <span>Mark C.</span>
Mark C.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

Great flexible product with pipelines as a first class feature

What do you like best?

I like that you can model whatever process you want, and that the fan in / fan out features allow you to run networks of processes in parallel in a predictable way. The dependency resolution allows you to run repeatable builds and reduce the amount of re-work you pipeline has to do.

What do you dislike?

The server component is not architected to scale across multiple servers, meaning it can be quite slow at a very large scale. Configuration is tricky to manage, as it is not yet possible to just check in a file describing your build process like you can with Travis for example.

Recommendations to others considering the product

Make sure you leverage templates. Don’t put your build code in the pipeline, use it to execute scripts in the project. Don’t use it for thousands of pipelines. Highly generalise and share your agents and avoid pipelines changing their state. Understand how to use secure environment variables and environments to maintain security. Don’t make everyone an admin.

What business problems are you solving with the product? What benefits have you realized?

Continuous integration and continuous delivery of enterprise applications and infrastructure code. Sharing of artifacts between projects and highly templated deployment processes.

Sign in to G2 Crowd to see what your connections have to say about GoCD
Headshots
GoCD review by <span>Jeremy O.</span>
Jeremy O.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

Good concept, flawed execution

What do you like best?

The product provides a ton of configurability, supports major dependencies and provides a reasonably good interface. Having built in test reporting was nice, and after some fiddling, it was easy to understand where everything was (build logs, test logs, etc).

What do you dislike?

Pipelines, stages, jobs, tasks. Which can run concurrently? Which are run sequentially? It's fairly opaque, in particular from the naming (and even rendering) what exactly happens when and is overkill for many tasks.

The way configuration is stored was extremely undesirable. I want simple text based configuration (YAML preferably) that I can version control and share easily. Not opaque XML that is largely configured through a web interface. Renaming even an existing task or something was more a matter of deleting the whole thing and recreating it, making for a pretty awful user experience.

What business problems are you solving with the product? What benefits have you realized?

Same problem as any. Repeatable, configurable, builds. The way in which configuration is defined ended up being a deal-breaker for me.

What Continuous Deployment solution do you use?

Thanks for letting us know!
GoCD review by <span>Daniela S.</span>
Daniela S.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

After some crafting setup, really nice and easy to use!

What do you like best?

Super easy to install and maintain.

The UI is really clean and it makes really easy to visualise where you are in the pipeline.

Also, the ability to extract templates from existing pipelines makes super-easy the addition of new projects.

What do you dislike?

The setup was a little bit crafty: first we had to understand how the general view of the product (environments, builds, tasks), then we had to write some ad hoc scripts to achieve what we wanted. It would be nice to have some built-in templates for the most common type of applications -- as far as I am aware there aren't any at the moment.

Also, the concept of environment didn't really fit the need of our team: we ended up using only one environment. Our pipeline was looking something like the following:

build > test > publish > deploy-to-staging > testing-on-staging > (manual sign off) > deployment-to-prd

Because of the structure of our pipeline, we could not manage to lock our pipeline as it was completing only when deploying to prd -- and obviously this wasn't happening for every candidate that was released.

This caused us some headaches when 2 pipelines of the same project were building at the same time.

What business problems are you solving with the product? What benefits have you realized?

We had the need of releasing frequently and quickly.

We wanted to automate the test and release process as much as possible so that this was not time consuming for the dev team.

Also, we wanted an infrastructure that a team of non-dev-ops could easily maintain.

GoCD review by <span>Bence N.</span>
Bence N.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

A great, modern alternative to Jenkins

What do you like best?

The clear overview of pipelines and their status on the web UI is the main reason we like Go CD. The materials, artifacts, and pipelines/jobs/tasks architecture is a very logical way to map a CD flow to. The REST API is also pretty powerful and makes automating things on Go CD a breeze.

What do you dislike?

Configuration/provisioning is a bit difficult to automate. The config file Go CD uses has a few parts that are host-specific, so you can't just render the same config file on a different host to have a working installation. Updating the configuration file automatically with external tools is similarly rather difficult to do, so if you're looking to track changes to your workflow in your devops config repo (with Ansible, Puppet, or the like) you should be prepared for spending some time on that.

Support for building GitHub pull requests is only available as a plugin and the software architecture was obviously not built with this use case in mind — for instance, you need to maintain separate pipelines for these builds, and your regular git builds. If this is your main use case, you might find TravisCI or CircleCI to be more fitting for you.

Using Go CD with non-Java projects feels a bit off, it doesn't seem to support build tools natively for any other platform.

Recommendations to others considering the product

Since we set up a Go CD server, an Ansible playbook has been published in the gocd-contrib/ansible-gocd GitHub repo. This makes initial setup way easier than before, so you can just install it and start evaluating the product in less than 10 minutes.

What business problems are you solving with the product? What benefits have you realized?

Go CD takes care of automated tests for pull requests and automated deployments whenever a changeset is accepted.

GoCD review by <span>Prachi G.</span>
Prachi G.
Validated Reviewer
Invitation from G2 Crowd
Reviewed On

Needs some minor improvements

What do you like best?

Building pipelines is extremely direct and it permits to structure your works in a reusable and convincing way is anything but difficult to utilize it contrasting with jenkins, Have better backing. Also, the capacity to concentrate layouts from existing pipelines makes super-simple the expansion of new ventures.

What do you dislike?

Support for building GitHub pull solicitations is just accessible as a module and the product engineering was clearly not worked on account of this utilization, for example, you have to keep up independent pipelines for these fabricates, and your normal git constructs. Configuration/provisioning is somewhat hard to mechanize.

What business problems are you solving with the product? What benefits have you realized?

Building a microservice design at scale, utilizing GoCD permitted us to scale the groups up and deal with our 50+ administrations organizations basically. Deployment times slice from hours to minutes aggregate some online libraries on different stages.

GoCD review by <span>Felipe C.</span>
Felipe C.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

Amazing experience, the truth pipeline!

What do you like best?

I loved the pipeline feature. It's amazing, incredibly useful and powerful. There's another killing feature that is pipeline templates, that makes my life a lot easier.

What do you dislike?

I disliked the UI, but my colleagues have a divergent opinion about it.

Recommendations to others considering the product

You must give a try about it. It's pipeline and template features are amazing, makes life a lot easier.

What business problems are you solving with the product? What benefits have you realized?

I'm solving problems of continuous integration and continuous delivery, making it a lot easier, with less configuration. It's incredibly easy to add new pipelines, even the complex one, with a little effort.

Kate avatar
Kate from G2 Crowd

Learning about GoCD?

I can help.
* We monitor all GoCD reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.