CZSOFT - kvalitní a dostupný software pro všechny

Jazyk: EN
Platforma: WIN, MAC, Linux
Distribuce: Elektronická licence

TeamCity server je testován v rámci následujících operačních systémů:
Linux
MacOS X
Windows XP
Windows Vista / Windows Vista 64
Windows 7/7x64

Údajně pracuje na:
Solaris 10
FreeBSD 7
IBM z / OS

1. Build steps

When creating a build configuration, you can now configure the sequence of build steps to be executed. Each build step is represented by a build runner and provides integration with a specific build or test tool. You can add as many build steps to your build configuration as needed.

2. New "My Changes" page

For TeamCity 6 release we have carefully re-thought a concept of the My Changes page, and did some radical changes towards usability and navigability. The new "My Changes" gives you a nice overview of how well your commit integrates in different builds and build configurations. It also supports keyboard navigation, which allows you to locate problems faster and in more comfortable way.

3. New IntelliJ IDEA projects build engine

TeamCity 6 uses rewritten build engine for IntelliJ IDEA projects, similar to the one found in IDEA itself. You can now run IntelliJ IDEA shared "run configurations" in TeamCity, and also produce all kinds of IntelliJ IDEA artifacts, including wars, ears, GWT artifacts, etc. Last but not least, IDEA projects in TeamCity can now be configured to only compile modules, required to run tests or produce build artifact, instead of recompiling and testing the whole project.

4. Support for Gradle and Maven 3

Gradle is a new promising build automation tool with lots of tempting features. We really like it, so we couldn't stand aside. Thanks to Gradle being extremely CI-friendly, we've managed to create a full-fledged Gradle build runner, which supports all of the advanced TeamCity features, and has unprecedented quality.

Another great news is that TeamCity 6 dedicated Maven support is now fully compatible with Maven 3.

5. Bundled plugin for an automatic build directory clean-up

Builds often produce a lot of garbage which should be cleaned before next build starts in the same directory. "Swabra" plugin remembers the state of the build checkout directory, and when next build starts in this directory, Swabra finds all of the files added by the previous build and removes them.