![]() ![]() If a change is found during the check, TeamCity automatically increases the VCS polling interval (the minimum after the increase is 15 minutes, maximum is 4 hours, increased by 2 times on each successful check). When a commit hook call comes in, TeamCity starts checking for changes in VCS roots which match the request. If you are using GitHub, try the external TeamCity Commit Hooks plugin OverviewĮven with commit hooks configured and working properly, TeamCity still makes requests for changes on the server start and on each build queuing (or starting) to ensure the latest changes are used even if commit hooks stopped to function. This way, TeamCity will make background requests for changes detection only when such changes are available. To avoid background polling, it is possible to set up a post-commit hook on the VCS server, which will notify TeamCity to start checking for changes procedure. For large installations with hundreds of VCS roots, this may create a noticeable load on the VCS server and on TeamCity. It periodically sends requests to the version control repository server to find out whether there are new revisions. Configuring VCS Post-Commit Hooks for TeamCityīy default, TeamCity uses a polling approach to detect changes in a VCS repository, that is for each VCS root. ![]()
0 Comments
Leave a Reply. |