JetBrains TeamCity Blog

The latest TeamCity 4.1 EAP build brings you support of continuous integration builds on Windows and Unix-based platforms under Mono framework.

TeamCity automatically detects presence of Mono frameworks installed and sets system properties which you can use when specifying the build settings and build agent requirements.

To instruct your build configuration use Mono framework, navigate to the Build Runner step when setting up or editing your build configuration and select:

• mono as a Target framework for NAnt,
• Mono xbuild as an MSBuild version for MSBuild,

Try Mono support by yourself downloading and installing the latest build and get further information in TeamCity online reference.

Technorati tags: TeamCity, continuous integration, build management, agile development, JetBrains, IntelliJ IDEA, Eclipse, MS Visual Studio 2005, MS Visual Studio 2008, mono

Here comes the progress summary of our last several weeks effort:

• With Microsoft Visual Studio plugin you can now perform pre-tested commit of your changes under Perforce
• Introduction of XML reporter allowing to process various XML reports and feed data to TeamCity
• Display of test details (particular test history in all build configurations) and problematic tests on the Project level
• Grouping of the tests list by package and test case
• Introduction of All Users group

Try a new build making a backup of your data before upgrade and read the detailed description of new features and improvements.

Wait for your feedback in TeamCity community.

Technorati tags: TeamCity, continuous integration, build management, agile development, JetBrains, IntelliJ IDEA, Eclipse, MS Visual Studio 2005, MS Visual Studio 2008, EAP

TeamCity has always provided a number of places and ways for monitoring changes which the team made:

• pop-up on the Projects page showing pending changes or those being built at the moment
• Recent history on the build configuration Overview page
• different types of notifications
• Change Log of the build configuration containing the records of all entries of changes which were committed.

In TeamCity 4.0 we made a number of improvements in the Change Log tab design helping to focus on what is the most important and letting you to:

• specify the range of changes you want to view by providing the range of builds
• show the builds where developers’ changes got into
• view changes which were made by a particular developer – the feature is available since TeamCity 4.1 EAP

Hope you will find these new Change Log features useful in your daily chores.

Before trying TeamCity 4.1 EAP we recommend you to backup your database as usual.

Technorati tags: TeamCity, continuous integration, build management, agile development, JetBrains, IntelliJ IDEA, Eclipse, MS Visual Studio 2005, MS Visual Studio 2008