The JetBrains Blog

Since version 2.0 TeamCity allows to specify the dependencies between the results of the builds of the build configurations, i.e. artifact dependencies and provides dependent builds triggering. When creating new builds, it's possible to use the artifacts of: last pinned build, successful build, …

IntelliJ IDEA introduces full-blown Spring and Hibernate support, Web services, Maven and ClearCase integration,Ruby & Groovy support, impressive performance improvements, and more productivity features October 15, 2007 Prague, Czech Republic, October 15, 2007 - JetBrains®, creators o…

In this EAP build we make the introduction to the role-based access to TeamCity features and also provide a number of improvements in other areas. The server administrators can now assign roles to users (available in Administration | User Accounts, particular user account page, Roles and Permissio…

TeamCity users can get notifications on different events of the projects they are watching, such as build start and failure, notifications on successfully completed builds or changing of the person responsible for the build failure. TeamCity has a number of means of notifying users on such events:…

We are glad to announce the new EAP release of TeamCity 3.0. This release provides a number of useful and long-awaited features. Search by the build number. The found builds are displayed in a pop-up window, and you can also view the found builds on a separate page: A brand new feature: build t…

Builds in TeamCity can be initiated by a variety of different triggers. These can be, for example, a change in the VCS, the successful build of another build configuration, or a schedule-based or manual trigger. Developers can also start personal builds with a pre-tested commit from their IDE. As so…

Java developers are encouraged to "Plug in and Win!" in the IntelliJ IDEAL Plugin Contest 2007 and compete for terrific cash and software prizes September 18, 2007 Prague, Czech Republic, September 18, 2007 — JetBrains®, creators of intelligent, productivity-enhancing applications, today …

As we mentioned in our previous blog post, TeamCity has a number of ways to verify the code quality. Searching for repetitive blocks of code - known as code duplicates - is one of them. The redundant and seemingly harmless pieces of code may eventually lead to an unmanageable project code base. Ou…

TeamCity has an unparalleled variation of means for maintaining code quality: search for duplicated pieces of code for Java and .NET projects (.NET support is now available in TeamCity 3.0 EAP) server-side code inspection of Java code (more than 600 IntelliJ IDEA's inspections are used) analysis…

Until now the build configuration used VCS roots that were defined in the project. Numerous TeamCity users asked for more flexibility when setting up the VCS roots, so we decided to make a number of refinements in this area. You asked, and we listened. :) First and foremost is that in TeamCity 3.0 …

TeamCity has multiple ways to monitor a projects health. First and foremost is, of course, the user dashboard. Then come the plugins for the IDE's that TeamCity currently integrates with (IntelliJ IDEA, MS Visual Studio, and Eclipse), standard e-mails, Jabber/XMPP protocol instant messages, and the …

TeamCity's Build Agents run the software builds and altogether make the company's Build Grid. To be able to run some build, the Build Agents must meet the requirements of the build configuration. If there is a free build agent matching the build configuration requirements is found when triggering t…