TeamCity 6.5: Free For Unlimited Number of Users
TeamCity Professional Edition is now rid of many previous limitations. Small and medium development teams can now run FREE TeamCity with an unlimited number of registered users, support for LDAP and NT authentication, and adjustable per-project permissions.
With this change we aim to make TeamCity even more affordable for many teams and startups.
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.
This feature is especially useful when some tests fail for a well known reason, but it is currently not possible to fix them. This could be inability to fix test soon, tests which are written before functionality, or so-called 'flickering' tests.
Muting tests is a potentially dangerous operation, that is why it is only available for Project Administrator role by default.
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.
TeamCity can now push the agent software to either Unix (by SSH) or Windows (with help of Sysinternals psexec) machine. Agent is also configured there to run on startup.
Remote Agent installation integrates with Amazon EC2 Cloud nicely too. TeamCity can automatically push agent software upon on-demand EC2 agent instance creation.
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.
If you are using Git or Mercurial, you can configure any specific build configuration to trigger Personal Build on any commit in one or multiple VCS branches. For watching multiple branches, TeamCity uses name pattern match.
Such builds are built on server remotely, but do not affect global build status and do not appear in other user's history.
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.
TeamCity now supports parametrization of VCS root settings, so that parameters could later be specified in the particular build configuration, or in a scope of a project.
This provides better flexibility and re-use of configuration settings.
Numerous .NET improvements
- AssemblyInfo patcher
- JetBrains dotCover results from TeamCity can now be rendered within Microsoft Visual Studio
- Native PowerShell scripts runner
- Built-in MSpec support
- Many other improvements and features for .NET teams
Read the full TeamCity 6.5 release notes »
TeamCity 6.0
December, 2010
- Build Steps
- New "My Changes" page
- New IntelliJ IDEA projects build engine
- Support for Gradle and Maven 3
- Lots of other improvements and fixes
TeamCity 5.1
April, 2010
- Improved support for .NET 4.0 and Maven
- Many features towards general usability
- Better server administration and configurability
- Enhanced IDE Integrations
- Stability improvements and bugfixes
TeamCity 5.0
December, 2009
- Amazon EC2 and Virtual Agents
- Better Support for Maven
- Per-test responsibilities
- Issue Tracker Integration
- Command Line Tool for Personal Builds
- Many other improvements and bugfixes