GoCD Reviews

Value Stream Map shows clearly the flows from code changes to production deployment

New GoCD configs have to be merged into master branch to take effect & there is no way to dynamically set parameters like environment variables per build.

GoCD is so easy to get started on. The documents are available & of high quality.

We're using GoCD for basic QA like building, testing, analyzing Pull Requests, as well as to build release packages, deploy them to test environments as well as production.

Simplicity, API, and of course the power behind concepts like pipeline, stage, jobs

I can say that is anything I don't like, but the thing to consider is that the projects I've used are not very big.

Keep Going and OpenSource, More Plugins

CI/CD Processes.

.Managing the agents to build the application and performance

UI part and handling the deployment configuration

Easy to intigrate with third party tools

Web interface is looking good.

You can organize well your builds using roles, environments, jobs, tasks, etc. .

You can use containers build agents.

Web interface needs improvements, doesn't run so good sometimes.

Using template files as a source of truth for pipeline stage creation.

Additional (YAML/JSON) template language support would be a nice to have

Staged deployment (dev/prod). The Manual deployment stages/gate keeping are a great saver.

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.

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

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

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.

The User Experience, and the functionality provided.

Takes some time to setup. Although become much better from previous versions. Not too many plugins present.

Best CD software. Much better than Jenkins and Travis, etc.

Continuous delivery and 1 step deployments.

is easy to use it comparing to jenkins, Have better support.

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.

Will be usefull to override some parameters from a template.

compile some online libraries on multiple platforms.

Building pipelines is very straightforward and it allows to structure your builds in a reusable and compelling way

It can be hard to get a grasp on how to structure pipeline dependencies and environment right

If you are doing continuous delivery, this is the tool for you

Building a microservice architecture at scale, using GoCD allowed us to scale the teams up and manage our 50+ services deployments in a simple way.

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.

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.