VCS trigger build from pre-tested commit


Now I'm using Teamcity 5.1.3, and the pre-tested feature works as expected from VS2010. However, to ensure security, I intend to add one more build configuration for VCS(I am using Perforce) trigger, so that the files directly submitted to Perforce are able to be tested as well. Then, I notice that after a successful pre-tested commit, the VCS trigger will detect the change and run the build again, which seems redundant for me. I wonder whether Teamcity has the ability to "remember" the build process run by pre-tested commit, and then suppress the perforce triggered build in this case.



1 comment
Comment actions Permalink


So far this is "as designed" behavior. An approach which prevents committing defective code into a build, so the entire team's process is not affected. Please read more at

Kind regards,


Please sign in to leave a comment.