ComponentSource Topic | TeamCity

TeamCity V6.5 introduces failing test muting

Thu, 02 Jun 2011 10:56:21 GMT

Configuring software tests using TeamCity.

Mute some of the failing tests so they wouldn't affect build status, allowing you to significantly reduce cluttering.

TeamCity is a server-based Web application that allows Java and .NET development teams to continuously integrate changes to the code base, frequently run distributed builds and tests, check and improve code quality, all the while making efficient progress toward successful project completion. TeamCity includes many productivity plugins for IntelliJ IDEA, Microsoft Visual Studio and Eclipse, which improves team collaboration without breaking the established practices, by separating creative work from routine tasks. TeamCity automates over 600 Java code inspections, code coverage and duplicates search. TeamCity allows to administer build infrastructures of literally any size from a central Web interface.

Updates in V6.5

Muting of failed tests
TeamCity introduces new means to mute some of the failing tests so they wouldn't affect build status, allowing to significantly reduce cluttering of the build information flow.
Tests grouping
Grouping tests by package is an essential feature for faster problem investigation. Tests can now be grouped in TeamCity on the build results page, current problems page, my changes page and so on.
Remote Agent Installation
TeamCity 6.5 provides a new, experimental way to remotely install build agents on the machines in your network, or in the cloud.
Restyled web interface
TeamCity 6.5 introduces new, restyled web interface - more lightweight, more modern looking and much more convenient.
Personal Builds on branches for Git and Mercurial
TeamCity 6.5 provides a more natural way to start Personal Builds on server with distributed version controls.
Parametrized Version Control System roots
VCS roots are collections of VSC settings used by TeamCity to obtain the source files for your builds. VCS roots do often get shared among different projects and build configurations.

About JetBrains

JetBrains have a passion for making people more productive through smart software solutions that help them focus more on what they really want to accomplish, and less on mundane, repetitive "computer busy work". As veteran Java developers, they felt bogged down by even the best tools they could find back in 2000. So they set out to build something better. From those first efforts came IntelliJ IDEA, which has been consistently honored with the industry's top awards. That's exciting of course, but what's even better is that Java developers the world over continue say that IntelliJ IDEA is simply the best and the most innovative IDE they have ever used. Its unprecedented refactoring support, intelligent coding assistance, and overall usability have helped thousands of developers to shed much of the traditional drudgery of coding, improve their productivity and code quality, and enjoy the craft of programming more.

TeamCity adds configurable build steps

Mon, 13 Dec 2010 17:30:00 GMT

Configuring the Build Runner in TeamCity.

Version 6.0 allows you to configure the sequence of build steps to be executed and features new My Changes page.

Updates in V6.0

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.
New "My Changes" page
For TeamCity 6 release JetBrains has carefully re-thought a concept of the My Changes page, and made 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.
New IntelliJ IDEA projects build engine
TeamCity 6 uses a 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.
Support for Gradle and Maven 3
Gradle is a build automation tool with lots of features. JetBrains has created a full-fledged Gradle build runner, which supports all of the advanced TeamCity features. TeamCity 6 now includes dedicated Maven support and is now fully compatible with Maven 3.
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.

For more information visit:
http://www.jetbrains.com/company/press/pr_011210.html

About JetBrains

JetBrains has a passion for making people more productive through smart software solutions that help them focus more on what they really want to accomplish, and less on mundane, repetitive tasks. As veteran Java developers, JetBrains developers felt bogged down by even the best tools they could find back in 2000, so they set out to build something better. From those first efforts came IntelliJ IDEA, which has been consistently honored with our industry's top awards. Java developers the world over praise IntelliJ IDEA as a highly innovative IDE. Its unprecedented refactoring support, intelligent coding assistance and overall usability have helped thousands of developers to shed much of the traditional drudgery of coding, improve their productivity and code quality and enjoy the craft of programming more.

TeamCity supports Maven Failsafe Plugin

Fri, 03 Sep 2010 17:29:00 GMT

Configuring the Build Runner in TeamCity.

Version 5.1.4 includes transparent support for Maven Failsafe Plugin reports.

Updates in V5.1.4

Now includes transparent support for maven-failsafe-plugin reports

About JetBrains

TeamCity supports Asia-Pac EC2 region

Mon, 14 Jun 2010 17:45:00 GMT

Configuring the Build Runner in TeamCity.

Version 5.1.2 also allows temporary disabling of email or Jabber notifications.

TeamCity is a server-based Web application that allows Java and .NET development teams to continuously integrate changes to the code base, frequently run distributed builds and tests, check and improve code quality, all the while making efficient progress toward successful project completion. TeamCity includes many productivity plugins for IntelliJ IDEA, Microsoft Visual Studio 2005 and Eclipse, which improves team collaboration without breaking the established practices, by separating creative work from routine tasks.

Updates in V5.1.2

Supports Asia Pacific EC2 region
Removed TEAMCITY_RAKE_RUNNER_MODE env variable requirement
You can now temporarily disable sending notifications via email or Jabber

About JetBrains

TeamCity improves .NET 4.0 support

Mon, 26 Apr 2010 21:42:00 GMT

Configuring the Build Runner in TeamCity.

Version 5.1 supports .NET 4.0, Visual Studio 2010 and TFS 2010 and adds code coverage support for Maven.

TeamCity is a server-based Web application that allows Java and .NET development teams to continuously integrate changes to the code base, frequently run distributed builds and tests, check and improve code quality, all the while making efficient progress toward successful project completion. TeamCity includes many productivity plugins for IntelliJ IDEA, Microsoft Visual Studio 2005 and Eclipse, which improves team collaboration without breaking the established practices, by separating creative work from routine tasks.

Updates in V5.1

Greatly improved support for .NET 4.0

.NET 4.0, Visual Studio 2010 and TFS 2010 are now supported;
All solution runners (except 2003) were merged into the one solution runner which includes support for Visual Studio 2010;
MSBuild runner now supports MSBuild for .NET 4.0;
.NET 4.0 is supported for tests runners. You can also choose the .NET framework version for NUnit runner;
NUnit tests UI is available in MSBuild runner;
NAnt 0.90 alpha 1 is supported;
Support for NUnit 2.5.3 and 2.5.4 added;
NUnit runner supports running each test assembly in its own process;
Enabled .NET Coverage report generation with the dedicated service messages.

Code coverage support for Maven

IDEA-based code coverage added for the Maven runner.
Coverage results can be seen on the Coverage report tab of the build and in the Coverage statistics chart for the build configuration.
In order for this feature to work properly, tests should run in the fork=true mode.
For the more information, check Code Coverage documentation section.
Maven artifact trigger now supports classifiers.

About JetBrains

TeamCity V5.0 released

Tue, 08 Dec 2009 17:05:00 GMT

Configuring the Build Runner in TeamCity.

Latest version adds support for Amazon EC2 and Virtual Agents, Issue Tracker integration and more.

TeamCity is a server-based Web application that allows Java and .NET development teams to continuously integrate changes to the code base, frequently run distributed builds and tests, check and improve code quality, all the while making efficient progress toward successful project completion. TeamCity includes many productivity plugins for IntelliJ IDEA, Microsoft Visual Studio 2005 and Eclipse, which improves team collaboration without breaking the established practices, by separating creative work from routine tasks.

Updates in V5.0

Amazon EC2 and Virtual Agents
Take avdantage of cloud computing with TeamCity by putting Build Agents on Amazon EC2. After your Build Agents' AMIs (Amazon Machine Images) are registered, the TeamCity server will account for those virtual machines in its build scheduling and will automatically do a suspend/resume job on them, based on the load and build queue status.
Better Support for Maven
Version 5.0 has many Maven support improvements under the hood. These include the creation of Maven-based build configurations (only the URL to the POM file is needed), the visualization of various project data gathered from POM, and a new type of dependency trigger - Maven artifact trigger. This type of trigger starts a build each time the specified Maven artifact changes.
Build Configuration Templates
Templates can save a lot of manual work when you need to define a number of duplicate or very similar build configurations. Now you can create a template with the common (shared) settings, and then inherit any number of build configs from this template. You can also extract a template from any of your existing build configurations.
Issue Tracker Integration
How often do you see comments like this: "TW-3431 fixed"? How about a little more detail on the issue at hand? The issue tracker integration provides an in-place bug title, direct navigation to the issue, and other productivity goodies. It is currently available for Jira, Bugzilla and JetBrains YouTrack out of the box, but can easily be extended to other systems via plugins.
Command Line Tool for Personal Builds
Previously, if you weren't using Eclipse, IntelliJ IDEA or Visual Studio, you were out of luck for missing one of the most important TeamCity features - Remote Run and Pre-Tested Commits. But things have changed. As the name suggests, now you can initiate the building of your local changes remotely on the server - from the local command line. No IDEs required. Command Line Tool is an experimental feature and can be downloaded as a separate plugin. It currently supports Perforce, Subversion, CVS, and TFS.

Many Other Improvements:

Per-test responsibilities
Build artifacts promotion
Dedicated change details/status page
Incremental update of the build log
Project archiving
Backup & Restore for easier TeamCity maintenance. Backup can be started from the UI or from the command line; Restore and Migration can be started from the command line only. Command line backup does not require stopping TeamCity if an external database is used.
Audit of user actions
Coverage support for .NET & Java. Based on IntelliJ IDEA coverage engine for Java and on NCover (ver 1, ver 3) or PartCover for .NET
Git & Mercurial support now bundled with TeamCity
Remote Run for Git from IntelliJ IDEA & Eclipse
Support for Cucumber, Shoulda, Test-Spec in Rake runner
TeamCity IntelliJ IDEA plugin now works with IntelliJ IDEA Community Edition and RubyMine

For more information visit:
http://www.jetbrains.com/company/press/pr_031209.html