We have our TeamCity enviroment set up to commit it's artifacts to SVN after a build has been done and tested.
We used to do this though MSBuild scripts, but have switched to using additional build steps. Once thing we have noticed, is that if any NUnit tests fail, the next build steps still run. This means we commit dll's which we know are broken, as tests have failed, not what we want to do. When using MSBuild, if a target errored, the script stopped.
Is there a way to get this to happen in team city? Some way for TeamCity not to do the next steps if the tests fail?
I suspect we could add a new build configuration which only runs if the main build runs, but this means checking out another copy of the project, and an additional build after each commit.