Incompatibility with GoCD version 20.2.0

[arminc]

Everything worked fine on GoCD version 20.1.0 but since GoCD 20.2.0 release gomatic can't create pipelines as it seems the configuration file is changed and it's not compatible anymore. Are there any plans to support it?

Example response:
RuntimeError: Could not post config to Go server (https://DNS/go/api/admin/config.xml) [status code=400] (and result was not json): <Response [400]>

[lobsterdore]

Did you ever get to the bottom of this @arminc? I am facing a similar error, however I believe it must be something to do with the config in place in GoCD, I have two GoCD deployments (a dev version and a prd version) and Gomatic is working for one but not the other.

[lobsterdore]

@leandrogualter any thoughts on this at all ^

[arvindsv]

FYI: There is a similar conversation happening on the GoCD mailing list: https://groups.google.com/d/topic/go-cd/7nmIWkO0QmY/discussion

[arminc]

Not yet, we paused the problem for now by using the old version. We still need to investigate why so we can upgrade.

[lobsterdore]

I can confirm that it's specifically version 20.2 with the issue, 20.1 is fine. When I get time I will put together something to reproduce this bug.

[alicekaerast]

Hi,

For those of you not subscribed to the related issue in the Go project - I have solved this problem, at least on the server I was dealing with today. It's Jetty filesize upload limits being reset by the wrapper properties file being overwritten.

I've still not got to root-cause, but I have managed to resolve this on our instance

gocd/gocd#7991 (comment)