branch remote run trigger vs pre-tested commit

can someone kindly explain what the purpose of a branch remote run trigger on a GIT repository?  As I see, you still have to commit & push for the trigger to start.
So this is not a pre-tested commit as the changes must get  pushed to the repo to activate the trigger.  Why does the documentation imply that this is an alternative to say, Subversion pre-tested commit

Of course Teamcity runs a personal build of the branch but so what?  Nothing is done with the changes. I still have to manually merge no?

2 comments
Comment actions Permalink

Hmm, seems we did not state in our documentation that this is a replacement to pre-tested commit. As name of this trigger suggests it's remote run for DVCs version control systems which can be used without IDE.
If you're looking for pre-tested commit like workfolow for DVCs, please take a look at automatic merge build feautre (added in 8.1): http://confluence.jetbrains.com/display/TCD8/Automatic+Merge

0
Comment actions Permalink

Thank you Pavel I understand.

0

Please sign in to leave a comment.