Maven

When you build a large project, it is often important that previously built components that are still up-to-date are not rebuilt. Otherwise, if all targets are built every time, each build will take a long time to complete. The longer it takes to make a build, the later you get feedback on your changes, the more difficult it is to setup reliable and meaningful Continuous Integration process. And the faster your builds are, the higher the rate at which your changes are integrated, the less is the feedback time, and the more value you get from your Continuous Integration. TeamCity 7.0 introduc

Today's TeamCity 7.0 EAP is the last EAP build with new features in it, as starting from it we are going to focus on fixing bugs and polishing already announced functionality. So basically, this build is more or less what TeamCity 7.0 is going to look like. So here's what we have for you today. REST API A feature request to allow build configuration editing via REST, that has been around for a while, has finally been implemented, so now you can get complete settings of a build configuration or template via REST and change them as well. Moreover, you can create and delete build configurations,

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

As the major TeamCity 6.0 release approaches, the release candidate build is already available. Besides bug-fixes, it contains several enhancements and improvements. For example: dotCover coverage engine now reports statement coverage instead of line coverage. .NET coverage options are now available in MSTest build runner. For each Maven build TeamCity agent gathers Maven specific build details, which are available on the dedicated "Maven Build Info" tab after the build is finished. Swabra settings now reside in a separate section called "Build Features" which is available on "Build Ste