Wir helfen Unternehmen seit 18 Jahren,
bessere Software zu finden
Was ist GoCD?
GoCD ist ein von ThoughtWorks entwickelter Open Source Continuous Delivery Server. GoCD bietet Unternehmen eine erstklassige Build- und Deployment-Engine für vollständige Kontrolle und Transparenz. Es wurde für eine kontinuierliche Lieferung konzipiert und die für diese Praxis wesentlichen Konzepte sind im Kern integriert. Enterprise Add-ons und professioneller Support von ThoughtWorks.
Wer verwendet GoCD?
Nicht vom Anbieter bereitgestellt
Du bist nicht sicher, ob GoCD das Richtige ist?
Mit einer beliebten Alternative vergleichen

GoCD
Bewertungen über GoCD
In Betracht gezogene Alternativen:
gocd - Totally changed our approach to development
Kommentare: Really a great product. As we had previously ported some-but-not all of our application stack to linux, once we had gocd up and running we were able to use it to accelerate and reduce errors in the porting of the hardest elements of our application over to linux. This isn't an advertised feature of the product or anything, but it's CD concepts are so clear that it became natural to just start out projects in GOCD rather than getting something working and then bringing it into the CI/CD platform. This is the real advantage of GOCD in our mind- everything is oriented so much around the pipline it lets you change your thinking to how things sound be, and then immediately do stuff in a more high-quality and automatic way.
Vorteile:
We previously used a version of an earlier product from same company (thoughtworks) called cruisecontrol (CC). We used CC for many years and it was a good product. When we started porting some of our servers from windows to linux as an experiment, we decided to simultaneously evaluate better continuous integration offerings to cruise control as a way to better-test our linux infrastructure. We looked at a number of products such as jenkins, travis and giblab. gocd was a pretty new offering at the time, but we felt it was a better solution than our existing CC installation and other CD/CI alternatives such as jenkins or travis. As we were in parallel porting our entire application to linux, and our application consistented of many different internal and external libraries, we wanted to be able to link everything up in a native CD (continuous development) platform from the get go. gocd didn't have the prettiest UI/UX (it's improved somewhat, but still takes a few days/weeks to get used to for newbies), but because it's a from-scratch CD product it can do things natively that many other platforms do in a more round-about way. it's pipelining concept being a fundamental configuration unit really matches how developers and designers think about and deploy software. Because the pipeline is a core element of gocd and everything is sort of designed around it, it's really quite thoughtfully done and intuitive from a conceptual standpoint.
Nachteile:
The configuration UI/UX is a bit clunky. This is a big area of focus for improvement for them, and it's gotten better but as far as software offerings in late 2019 go there's some to be desired. It probably took at least a week for average person to get comfortable using the web interface. You can skip the web interface and config directly from either command line, xml and they do support git-management of both. (we don't use these presently for other reasons, but they're there)
My experience from 3+ years ago
Kommentare:
Overall it was ok, we also used travis and jenkins at the time. travis was in another league, it's paid, a service, it had another approach, jenkins was worst than gocd, they created the blue project to make it better and it wasn't perfect, but for us it became better than gocd, but we still had projects using gocd.
Later i left the company and started to use gitlab pipelines, GitHub workflows, travis, hosted solutions so i'm not very familiar with gocd nowadays, but at the time it was one the best solutions i used.
Vorteile:
At the time i used it (it was a 3+ years ago), it had the best UI comparing with most of the competitors, at least the self deployed ones. It was easy to use, it supported plugins.
Nachteile:
It didn't had support for describe our process as code, but we used a plugin for that, that give us some issues at the time that we had to deal with, but no big deal. I remember that we switched to jenkins using theirs Jenkisfile because it had better fit on our workflow. i remember that the deployment process was not the best also. regarding the agents, the replication of them, or how to support more wasn't ideal, i remember that at the time we developed a script to automate that, but it was very tricky.
Good for small projects, but doesn't scale very well
Kommentare: Mixed feelings about GoCD, as on one side it provides nice visual feedback about the pipelines, on the other side whenever something went wrong it was a pain to fix. It also didn't scale well on our case when the number of pipelines and projects grew.
Vorteile:
- free - pipeline graph is nice - multiple pipelines (although single XML config is a problem) - cross platform
Nachteile:
- single XML configuration for all pipelines, which is brittle and error prone - no support for declarative pipelines - hard to maintain - user interface is not intuitive - slow - agent setup is cumbersome
In Betracht gezogene Alternativen:
GOCD
Vorteile:
GOCD provides most reliable solution for fast delivery.
Nachteile:
Lots of configurations.some custom plugins does not support
GoCd - Easly deploy your apps
Vorteile:
It is easy to connect with github using addons and manage groups and permissions.
Nachteile:
When you have too many pipelines you might face limitations with gocd config file size.
Nice Product
Vorteile:
It help lot to manage our continouse delivery process
Nachteile:
Source integration need to develop for easy connectivity
Great software for building pipelines the right way
Kommentare: more reliable and reproducible builds.
Vorteile:
GoCD really encapsulates the true spirit of continuous delivery and makes it easy to do things the right way and harder to set things up the wrong way. Artifacts are only ever built once. Open source is a big plug.
Nachteile:
Young product, not as many plugins as competitors like Jenkins, Hopefully that will change over time. It also uses a bit more memory than Jenkins which can be a problem if it runs on Windows VM. Also it is written using spring framework which your developers might not be familiar with.