A WebHook POST is triggered when a build. Go to build configuration and set Minimum checking interval to 99999999: Conclusionīy settings up a Webhook, we were able to reduce the load on version control system server and save deployment time by having an immediate build triggering. tcWebHooks is a plugin for TeamCity which allows project admins to configure webhooks for a project in TeamCity. By the time I'm writing this article there is no option to completely disable pull, but we can set checking time interval to 99999999 seconds, which is ~3 years and can be treated as eternity in our case. However, TeamCity will still do a pull, because we didn't disable periodic checking. In the documentation I did not find anything related to the settings for getting webhooks. I have already done this and the GitHub sends me such requests: 'POST /webhooks/endpoint.html HTTP/1.1' 204 0 '-' 'GitHub-Hookshot/6031d40' '192.30.252.38' But TeamCity does not understand them at all. It's a good idea to create a separate user for this need. As I understand, I need to setup webhooks on GitHub. Basically, you need to send a POST request with the following format: URL above can be used to register a Webhook on each Repository push. Starting from version 8.1 TeamCity ships with its own REST API. Having a delay with 30 seconds is infiniteness. On average you should wait 30 seconds before TeamCity will notice the change and trigger a build. It produces unnecessary load on version control server.

However, it's not a best practice to use a pull, because: It means that it will go to the VCS periodically and look for any updates.

Teamcity webhook