Where Does GoCD Store Pipelines and History?
Where self hosted GoCD keeps pipelines in database on Linux servers. Exact folders are covered below.
Last updated
GoCD is pipelines with server storage. The database holds materials, stages, and run history. Artifacts sit beside it in configured stores.
Same database means same pipelines. Exact paths vary by zip versus package installs. Keep backups of database plus artifacts together. One without the other restores definitions without run logs. For moves, stop services first to avoid partial dumps. Screenshots of settings help when support asks for reproduction steps later. Check the in app storage readout when sizes look wrong on different releases.
Where GoCD Server stores this, by platform
/var/lib/go-server (database, artifacts per config)
Pipelines live in the server database with run history. Back up the database stopped. Match releases before restore. Artifacts sit in configured stores.
Frequently asked questions
How do I migrate GoCD to a new server?
Back up the GoCD database plus config directory with services stopped, then install the same release on the new server before restore. Pipelines follow the database. Mixed releases can refuse old schemas, so match versions first.
Does GoCD back up run history?
Yes, in the server database per pipeline with run history attached. The host holds a working copy plus artifact cache. Views rebuild after restore. Export XML configs from admin settings for records, since the data directory alone is working state.
Notice an outdated path? Let us know.