GoCD coordinates the stages that turn source changes into a release, including jobs that depend on artifacts produced by other pipelines. Its server tracks that workflow while agents perform the actual build and deployment work. It is useful when a delivery process needs an explicit view of those dependencies. This second historical URL describes the same GoCD product, with the guidance below focused on preserving an existing server and its pipelines during an upgrade.
Deployment and operating notes
The recovered gocd-2 page links the same GoCD project and chart architecture as the other GoCD entry. No evidence establishes a distinct product edition behind the suffix. GoCD now has its own official Helm repository, and the old instruction to grant Tiller permissions belongs to Helm 2 rather than a current installation.
For an inherited GoCD server, capture server version, configuration repository, database, artifacts, plugins and encryption material before upgrading. Inventory static and elastic agents and the tools that builds assume are installed. Rehearse server restoration with the matching version, then follow the project’s supported upgrade path and plugin compatibility guidance. Validate pipeline scheduling, dependency triggers, secrets, artifact retrieval and agent registration. Prevent the restored test server from launching production deployments or receiving live webhooks during rehearsal. Keep a coordinated pre-upgrade backup because reverting a chart may not reverse database or plugin changes. The historical duplicate URL remains useful for existing readers without inventing a separate GoCD product.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
GoCD is an open-source continuous delivery server to model and visualize complex workflow with ease. This chart bootstraps a single node GoCD server and GoCD agents on a Kubernetes cluster using the Helm package manager. This is the main repository for GoCD – a continuous delivery server. GoCD helps you automate and streamline the build-test-release cycle for worry-free, continuous delivery of your product.
Prerequisites
- Kubernetes 1.8+ with Beta APIs enabled
- PV provisioner support in the underlying infrastructure
- LoadBalancer support or Ingress Controller
- Ensure that the service account used for starting tiller has enough permissions to create a role.
What can we do?
End to End Visualization
GoCD’s value stream map shows your entire path to production in a single view. Easily navigate across jobs, spot inefficiencies, and optimize your process.
No plugin required, out of box CD.
Cloud Native Deployments
GoCD streamlines your CD workflow on popular cloud environments such as Kubernetes, Docker, AWS and more.
Complex Workflow Modeling
GoCD excels at modeling complex CD workflows for fast feedback with its modeling constructs, parallel execution and dependency management.
No plugin required, out of box CD.
Advanced Traceability
GoCD helps you troubleshoot a broken pipeline by tracking every change from committing to deploy in real time. Compare content – both files and commit messages – across any two arbitrary builds. No plugin required, out of box CD.
Features:
Model complex workflows
With its parallel and sequential execution, GoCD can easily configure dependencies for fast feedback and on-demand deployment. Its fan-in/fan-out dependency management always does the “right thing,” avoiding spurious builds.
Promote trusted artifacts
Every pipeline instance is anchored to a particular changeset. GoCD makes it easy to pass once-built binaries between stages so you know exactly what’s being deployed and that the binary has been tested.
See how your workflow really works
GoCD’s real power is in the visibility it provides over your end-to-end workflow. GoCD’s Value Stream Map lets you track a change from committing to deploy at a glance. And when things go wrong, it’s easy to see both the upstream cause and the downstream effects.
Deploy any version at any time
GoCD’s manual triggers allow you to deploy any known good version of your application to wherever you like. This increases the reliability of pushing to production and empowers QA teams with self-service environments. And, if necessary, it’s securable and auditable.
Run and grok your tests
Verification is a key piece of any deployment pipeline. GoCD will execute tests written in most languages or frameworks. GoCD’s agent grid provides parallel and cross-platform execution. GoCD’s test reporting will tell you in exactly which changeset and on which platform a test started breaking, which comes in extremely handy when fixing a complex broken build.
Compare builds
GoCD’s compare builds feature can provide a simple bill of materials for any deployment. Perhaps more powerful is its ability to compare the content – both files and commit messages – across any two arbitrary builds. This is invaluable when troubleshooting a broken pipeline.
Eliminate bottlenecks
GoCD’s agent grid eliminates bottlenecks, providing trivial parallel execution across pipelines, platforms, versions, branches, etc.
Keep pipeline configuration tidy
Easily reuse pipeline configurations via GoCD’s template system. This makes managing pipelines for versions and branches easy as pie.
Trust your team
While most enterprise applications go overboard with their permission model, GoCD seeks to provide just enough. In particular, GoCD supports auditable deployment and can delegate the configuration of pipelines to users without full-blown admin privileges.
GoCD open source plugins
GoCD has extension points for which plugins can be created. There are numerous plugins already available, or if you don’t see what you need, you can write your own.
Sources & further reading
Spotted something that needs another look?
Help improve this page →