GoCD not update parameters and not create , delete piplines

13 views
Skip to first unread message

ashok reddy C k

unread,
Mar 13, 2026, 4:23:46 AMMar 13
to Chad Wilson, go...@googlegroups.com
Hi Team,

We noticed that the file size exceeded 50 MB last week. We took action by stopping the service and enabling maintenance mode. Subsequently, we deleted a few pipelines (inline) that had not run in the last 365 days, which reduced the file size to 42 MB out of a total of 10,000 pipelines.

However, the XML file is still increasing daily. As of today, the size is 469,020,56 bytes as of March 13 at 08:06 for the cruise-config.xml file.


Could you please provide any solutions for a permanent fix for the "Size Exceeded" error?

Chad Wilson

unread,
Mar 13, 2026, 4:48:03 AMMar 13
to go...@googlegroups.com
Could you look at https://github.com/gocd/gocd/issues/new/choose (bug report) for an example of the type of information that's needed to help. It's rather difficult without basic information about your installation.

What's the full error as displayed? Where was the error? via UI or API?

Anyway, would really need the specific error and some analysis of your own as to what chunks are consuming most space, or details from /go/api/support, or a redacted version of the XML to give any specific suggestions.

Assuming pipeline definitions are all in the config.xml, especially at that # pipelines you should probably be migrating your pipelines to pipelines-as-code where the pipelines are saved as YAML or JSON or jsonnet etc and stores in separate source control. Pipelines maintained via config repos are not affected by such limits, and are generally much faster/easier for your GoCD to work with.

-Chad
Reply all
Reply to author
Forward
0 new messages