TeamCity causing performance issues on Github Enterprise service

Hi,

I wanted to see if anyone else is using TeamCity with Github Enterprise and is experiencing some performance issues related to TeamCity opening a lot of ssh connections to the github service.  The suggestion the github enterprise folks have suggested is to use service hooks instead of teamcity constantly checking our github enterprise service.  Any way to tell TeamCity to reuse an ssh connection to avoid multiple connections being made to the service?  Anyone else running into this issue?  Any downsides to using the service hooks instead of the vcs triggers?  My worry is that if we have to convert to service hooks it would require a huge effort to go and update every build configuration that uses the vcs trigger to now use a service hook.

Thanks,
Jay

Please sign in to leave a comment.