IntelliJ IDEA

The release of TeamCity 7.1 is so far planned for mid-June, and today we launch the early access program, so don't sit on your hands - grab the first EAP build while it's hot! Today's menu includes: Current problems: now on Overview page If you need to monitor problems in many build configurations, you can now get the whole picture right on the overview page without having to expand each and every build configuration in question: Sticky investigations Normally an investigation assigned for a build configuration or a test is automatically cleared once the build configuration becomes green o

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

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