Incompatible with TeamCity 2018.1.2 #112
Comments
|
Thanks for the heads up. Updating TeamCity to 2018.1.2 now to check. |
netwolfuk
added a commit
that referenced
this issue
Sep 1, 2018
The most recent version of the ExceptionMapperUtil file is extracted from the SVN history, and copied into the project locally. This is a temporary workaround to address https://youtrack.jetbrains.com/issue/TW-56626 and #112 The actual problem is caused by the removal of src/jetbrains/buildServer/server/rest/jersey/ExceptionMapperUtil.java. The replacement appears to be to extend ExceptionMapperBase instead, however the ExceptionMapperBase class appears to force the response to be text/plain, because it takes a ResponseData object and builds a Jersey Response object itself. Previously, we were free to return our own Response object, and could serialise the response as JSON or XML if that was helpful.
|
Hi @htonheim. As mentioned on the YouTrack ticket, removing the Web Hooks REST API (tcWebHooks) plugin from the Administation -> Plugins page on the TeamCity server and restarting TeamCity will resolve this issue. You do not need to uninstall the Web Hooks (tcWebHooks) plugin. I am testing a fix for this issue at the moment, and hope to do a release shortly. |
|
New release available: https://github.com/tcplugins/tcWebHooks/releases/tag/v1.1-alpha18.241.356 |
|
Issue is resolved by new release. |
netwolfuk
added a commit
that referenced
this issue
Sep 11, 2018
The most recent version of the ExceptionMapperUtil file is extracted from the SVN history, and copied into the project locally. This is a temporary workaround to address https://youtrack.jetbrains.com/issue/TW-56626 and #112 The actual problem is caused by the removal of src/jetbrains/buildServer/server/rest/jersey/ExceptionMapperUtil.java. The replacement appears to be to extend ExceptionMapperBase instead, however the ExceptionMapperBase class appears to force the response to be text/plain, because it takes a ResponseData object and builds a Jersey Response object itself. Previously, we were free to return our own Response object, and could serialise the response as JSON or XML if that was helpful.
netwolfuk
added a commit
that referenced
this issue
Apr 10, 2024
The most recent version of the ExceptionMapperUtil file is extracted from the SVN history, and copied into the project locally. This is a temporary workaround to address https://youtrack.jetbrains.com/issue/TW-56626 and #112 The actual problem is caused by the removal of src/jetbrains/buildServer/server/rest/jersey/ExceptionMapperUtil.java. The replacement appears to be to extend ExceptionMapperBase instead, however the ExceptionMapperBase class appears to force the response to be text/plain, because it takes a ResponseData object and builds a Jersey Response object itself. Previously, we were free to return our own Response object, and could serialise the response as JSON or XML if that was helpful.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
TeamCity should work.
Current Behavior
TeamCity UI breaks down completely. teamcity-server.log is full of "Unexpected response while executing internal Rest API request". See https://youtrack.jetbrains.com/issue/TW-56626.
Steps to Reproduce (for bugs)
Your Environment
The text was updated successfully, but these errors were encountered: