The JetBrains Blog
build failure conditions
Now we see dead code too!
"I see dead code" - .NET developers all over the world know this slogan due to incredible code analysis feature provided by JetBrains ReSharper. One of the most wanted TeamCity features was to have .NET inspections results right on build server. Starting with the latest EAP you have it! The only thing you need to do to get all the benefits of ReSharper's analysis right in TeamCity is to add Inspe
Fail build on specific log message
Previously described Fail build on metric change feature is not the only new way of controlling build status and detecting build failures. In TeamCity 7.0 we introduce one more useful feature that allows to mark build as failed, in case when certain line is met in build log. When starting various processes within a build TeamCity monitors their status by inspecting exit code and performing some ot
Opening TeamCity 7.0 EAP (build 20184)
Look out world, we have just opened early access program for the next TeamCity version: code name Faradi. That means you can download the first TeamCity 7.0 build right away and try all the cool features that are in it. Want to know what features are there? Here's a list: Build Failure Conditions - Smart Control Over Your Build Status TeamCity has become smarter in deciding when a build is to be c