We just raised a $30M Series A: Read our story

What needs improvement with GoCD?


Please share with the community what you think needs improvement with GoCD.

What are its weaknesses? What would you like to see changed in a future version?

ITCS user
11 Answer

author avatar
Top 5LeaderboardReal User

* If the workflows were updated for any reason, such as when environments are created, deleted, or changed, the previous delivery pipelines will be broken. You can't redeploy the old version or propagate new versions to the following environments. * It would be great to have more flexibility in configuring the initial job. We are using GoCD for the CD process only, so any jobs are triggered by external CI tools, not the GoCD itself. We don't need to configure code repositories or other inputs that GoCD is expecting, so we are forced to create the dummy repository, and the commit history is not relevant to the CD process. * It would be great to have more available plug-ins to cover more functionality inside GoCD. * The documentation really should be improved by including real examples and more setup cases.

Find out what your peers are saying about Thoughtworks, Microsoft, Atlassian and others in Application Lifecycle Management (ALM) Suites. Updated: October 2021.
552,136 professionals have used our research since 2012.