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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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). Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

I disliked the UI, but my colleagues have a divergent opinion about it. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

The User Experience, and the functionality provided. Review collected by and hosted on G2.com.

Takes some time to setup. Although become much better from previous versions. Not too many plugins present. Review collected by and hosted on G2.com.

Building pipelines is very straightforward and it allows to structure your builds in a reusable and compelling way Review collected by and hosted on G2.com.

It can be hard to get a grasp on how to structure pipeline dependencies and environment right Review collected by and hosted on G2.com.

is easy to use it comparing to jenkins, Have better support. Review collected by and hosted on G2.com.

sometimes the ui is not responsive. More help about how to configure the MacOSX and linux agents. For example on MacOSX you need to do some tricks to install java 1.8.0 and make it to be the default java after a startup. Review collected by and hosted on G2.com.

The pipeline concept. Really helps to visualise the steps of your CD pipeline, and the progress of each commit from push-to-master to deployed to production. Review collected by and hosted on G2.com.

Doesn't scale. With more concurrent users, making changes to the pipeline configuration becomes unbearably slow. Only use if you are a small team, or create an instance per small team. Review collected by and hosted on G2.com.