Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Branch Remote Run trigger automatically starts a new personal build each time TeamCity detects changes in particular branches of the VCS roots of the build configuration.
At the moment this trigger supports only Git and Mercurial VCSes.

For non-personal builds off branches, please see Working with Feature Branches. When branch specification is configured for a VCS root, Branch Remote Run Trigger only processes branches not matched by the specification.

A trigger monitors branches with names that match specific patterns. Default patterns are:



At the moment there is no UI to show what's going on inside the trigger, so the only way to troubleshoot it is to look inside teamcity-remote-run.log. To see a more detailed log please enable debug-vcs logging preset at Administration | Server Administration | Diagnostics page.

In order to trigger a build branch should have at least one new commit comparing to the main branch.


If your build configuration has 2 VCS roots which support branch remote-run and you push changes to both of them, TeamCity will start 2 personal builds with changes from each root.

See also:


Administrator's Guide: Git | Mercurial