This post describes one of the new features in the upcoming TeamCity 8.0 Using TeamCity, we can easily set up a build farm using a central TeamCity server and several connected build agents. By having multiple build agents, we can run builds and build configurations in parallel. Different branches of the same project can build simultaneously on different build agents,  personal builds can be run on one build agent while the nightly build is running on another agent and so on. But what if we have multiple build agents and we want to constrain parallelism for some projects? What if we do want t

New TeamCity 7.0 EAP build is ready and waiting for you to try! We have improved features introduced in the first EAP build, and of course we've got some completely new stuff. .NET Inspections runner Yes, it's finally here and it's based on powerful ReSharper code analysis engine! Now you can run .NET inspections and see the results right in TeamCity. Global Maven settings Previously you could specify path to alternative user settings file (equivalent to Maven command line option -s or --settings) in build configuration.  Now you can define these settings xml files globally in Server Configu

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 considered "failed" - now it can look beyond the obvious like exit code or failed tests presence. Basically, you can instruct TeamCity to mark a build as failed if it has become "worse". There is a num