GoCD Reviews & Product Details

I have been using GoCd for the past 1 year. I have been using it as the main pipeline for all our deployments. Features like giving access to different users, feature to create different templates for different pipelines, having a variety of version control systems and the ability to integrate tool and testing frameworks really makes it stand apart. Review collected by and hosted on G2.com.

When I first started using GoCD, learning all the features was hard due to the low user base. The user interface sometimes feels complex, especially for beginners to set up specific and intricate pipeline configuration, also for which tutorials are hard to find. Review collected by and hosted on G2.com.

GoCD makes the continuous delivery just simple as we can have many agents within the same server also the pipelines are very easy to configure from the code first approach. So, I would highlight those as the best features. Review collected by and hosted on G2.com.

It had a slide with more learning curve to set up, I guess there should be an improved onboarding guide. Review collected by and hosted on G2.com.

Value Stream Map shows clearly the flows from code changes to production deployment Review collected by and hosted on G2.com.

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

Simplicity, API, and of course the power behind concepts like pipeline, stage, jobs Review collected by and hosted on G2.com.

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

- The templating was nice once one you got the hang of it

- Triggers/DAG of pipelines is solid if you have to do massive deployments with the push of a button Review collected by and hosted on G2.com.

- API and templating support is pretty rough

- doesn't have the best integration with Github, for which we had to use AWS CodeBuild for webhooks

- UI/code setup for a pipeline is pretty complex for new people Review collected by and hosted on G2.com.

1. Web interface is user-friendly.

2. Using templates is easy once you understand it.

3. You can use containers build agents. Review collected by and hosted on G2.com.

Nothing to dislike but areas of improvment

1. UI can be improved a bit.

2. Additional support of YAML template will help a lot.

3. Configuration is a bit rough to understand. Review collected by and hosted on G2.com.

Managing the agents to build the application and performance Review collected by and hosted on G2.com.

UI part and handling the deployment configuration Review collected by and hosted on G2.com.

Web interface is looking good.

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

You can use containers build agents. Review collected by and hosted on G2.com.

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

Integration with docker containers and kubernetes should be improved. This integration process should be smoother. Review collected by and hosted on G2.com.

Visually way better compared to Jenkins and Travis.

Intuitive. Review collected by and hosted on G2.com.

Not powerful as Jenkins in terms of plugins.

Not easy setup as Jenkins. Review collected by and hosted on G2.com.

Using template files as a source of truth for pipeline stage creation. Review collected by and hosted on G2.com.

Additional (YAML/JSON) template language support would be a nice to have Review collected by and hosted on G2.com.