Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatibility with GoCD version 20.2.0 #69

Open
arminc opened this issue Apr 9, 2020 · 6 comments
Open

Incompatibility with GoCD version 20.2.0 #69

arminc opened this issue Apr 9, 2020 · 6 comments

Comments

@arminc
Copy link

arminc commented Apr 9, 2020

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
Copy link

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
Copy link

@leandrogualter any thoughts on this at all ^

@arvindsv
Copy link

arvindsv commented Aug 7, 2020

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

@arminc
Copy link
Author

arminc commented Aug 8, 2020

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

@lobsterdore
Copy link

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.

@kaeraali-flutterint
Copy link

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants