GoCD is an open-source continuous delivery server, licensed under Apache-2.0 and sponsored by Thoughtworks, Inc., that automates and streamlines the build-test-release cycle for teams that want to model, run, and control their own delivery pipelines.

What it is

GoCD is a continuous delivery server, and the repository gocd/gocd is its main repository. It is predominantly a Java and TypeScript project that uses Spring Framework, SparkJava, and MithrilJS as key frameworks, is built with Gradle and Webpack, and runs within Eclipse Jetty. A small number of older parts of GoCD are rendered server-side within JRuby on Rails, using legacy plain JavaScript with JQuery. The project carries the Apache License, Version 2.0, is sponsored by Thoughtworks, Inc., and is registered with the topics cd, ci, ci-cd, continuous-delivery, continuous-delivery-server, continuous-deployment, continuous-integration, continuous-testing, gocd, and infrastructure-as-code.

The concrete problem it solves is the coordination of the build-test-release cycle itself: instead of leaving release sequencing to separate CI jobs, manual steps, and hand-run scripts, GoCD provides one server that owns the pipeline from build through test to deployment, with continuous integration, continuous testing, and continuous deployment as the stages it covers. The repository also demonstrates that model on itself, because GoCD itself is used to build GoCD at build.gocd.org.

Key capabilities

• Runs as a continuous delivery server that automates and streamlines the build-test-release cycle for continuous delivery of a product.
• Ships an official server image, gocd/gocd-server, published on Docker Hub, with pull counts tracked on the repository badges.
• Provides a Test Drive GoCD quick start that lets a new user build a first pipeline while learning key GoCD concepts.
• Distributes server downloads through the project downloads page at gocd.org/download.
• Documents a self-hosting loop in which GoCD is used to build GoCD, hosted at build.gocd.org.
• Maintains a formal security policy in SECURITY.md covering GoCD's security status and responsible disclosure of issues.
• Publishes a contributor's guide and a separate guide to setting up a development environment at developer.gocd.org/current/.

Who uses it and how

• Platform and delivery teams that need a self-operated continuous delivery server rather than a hosted pipeline service.
• New users who start with Test Drive GoCD to build a first pipeline before committing to a full install.
• Operators who deploy the server from the gocd/gocd-server Docker image and track image pulls as a deployment signal.
• Contributors who build a development environment using the guide at developer.gocd.org/current/, working in Java, TypeScript, Gradle, and Webpack.
• Teams that treat pipeline definition as infrastructure as code, which the infrastructure-as-code topic marks as an intended use.

Getting started

Pull and run the server image gocd/gocd-server from Docker Hub, or download an installable build from the downloads page at gocd.org/download. To build a first pipeline while learning GoCD concepts, use Test Drive GoCD at gocd.org/test-drive-gocd.html.

How it compares

No list of paid products that GoCD replaces is provided in these facts, and no comparable tools are named alongside it. On the evidence available, GoCD stands alone in this registry as a continuous delivery server.

When to use it — and when not to

Choose GoCD when the delivery pipeline must be owned and operated in-house and the team is comfortable running its own server, since the facts describe an install-and-run model through downloads or the gocd/gocd-server image and name no hosted service. Expect to lean on external material: the README is deliberately brief and points to docs.gocd.org for user help, so most operational detail lives outside the repository. Teams that want a fully managed service with no server to run should look elsewhere, and anyone building from source should note that parts of the codebase remain on legacy JRuby on Rails with JQuery.