Github integration with TeamCity 2017 is failing
Hi,
We recently upgraded to 2017 version of TeamCity from version 10.0.1. The upgrade itself has gone smoothly.
However after the upgrade, we see that the service integrations that we had setup between our Github Enterprise instance and TeamCity has started failing with a 405. Looking at our Github logs, it looks like the TeamCity integration that we have in Github is now no longer compatible with TeamCity 2017, probably because of this
"if you use non-bundled clients which perform HTTP GET requests to TeamCity, some of the GET requests (those which change the state of the server, like http://server/action.html?add2Queue=XXX) stop working in 2017.1, please change the requests to use POST instead of GET;"
Given that we were using the built in Github teamcity integration, we don`t really have the option of changing the Get to a Post.
Looking through it some more we found this post https://blog.jetbrains.com/teamcity/2016/09/installing-github-webhooks-from-teamcity/, which kinda looks like what we need.
After downloading the plugin into the plugin directory , and restarting the server, I can confirm that the plugin is loaded
But I don`t see any of the options that this tool should be providing me. When I click on my projects I see the standard webhook dialog, but not the new drop down dialog as is documented here https://blog.jetbrains.com/teamcity/2016/09/installing-github-webhooks-from-teamcity/
What could I be doing wrong ? Basically I would like commits to github to kick-off certain builds in teamcity. How do we do this in case there is a new way to do so?
Please sign in to leave a comment.
Hi Alok,
First, the Github integration is bundled, so the "if you use non-bundled" should exclude it. You need to have the connection to the github enterprise set up on the project. If the integration that we provide bundled is not working, then that maybe a bug or a misconfiguration. As the blog post states, a connection to the github enterprise is required for the extra options to show up, so if you don't set it up, it won't work either.
Could you share screenshots of the github enterprise configuration? If you could also check the server logs for the full stacktrace on the 405 error, that would also be helpful.