
JetBrains TeamCity Enterprise v6.5 | 309.3 Mb
TeamCity is a continuous integration & build management solution which, following the tradition of IntelliJ IDEA, takes software team productivity to a whole new level. It automates and coordinates key collaborative processes to eliminate manual systems and delays, providing tight integration with multiple build and test tools, real-time unit test frequency, server-side inspections and code coverage analysis. TeamCity is a continuous integration and build management system. With TeamCity, you can set up a build server within minutes and enjoy out of the box continuous unit testing, code quality analysis, and early reporting on build problems — even without leaving your favorite IDE. TeamCity offers a gentle learning curve, so you can quickly improve your release management practices by gradually adopting its advanced features and capabilities.
Build Grid uses a computing grid to run parallel builds on multiple Build Agents with different platforms
Amazon EC2 integration for rapid Build Grid scaling
Pre-tested commits help avoid breaking the code in the repository and optimize the code integration cycle
On-the-fly test results reporting with intelligent tests re-ordering
Build configuration templates for easier builds replication
Over 600+ automated server-side inspections for Java, JSP, JavaScript and CSS
Comprehensive server configuration and Build Grid management console
Role-based, per-project user administration with user groups support
LDAP support with automatic user profile synchronization Assigning and taking responsibility over the broken builds
Configurable per-user and per-user group notifications
Detecting hanging builds, with a thread dump to help investigate the cause
Customizable statistics on build duration, success rate, code quality and custom metrics
Change history browsing with a Diff Tool and "History" builds
Integration with issue tracking systems: JIRA, Bugzilla and JetBrains YouTRACK out of the box, more with 3rd party plugins
Dedicated support for Maven and Gradle build systems
Integrated code coverage and duplicates finder for Java and .NET
Integration plugins for most major IDEs with automatic navigation between the web browser and your IDE
Support for .NET, Java and Ruby
What's new in TeamCity 6
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.
6. Much more, including...
Build priorities in the build queue, and priority classes for managing them
Improved support for RVM and Bundler for building Ruby/Rails projects
Bundled JetBrains dotCover .NET coverage engine
Updated IDE integrations with lots of new goodies
New TeamCity upgrade procedure, and many other usability improvements
Home Page
uploading
fileserve