Read the second part of the series here.
How quick and easy it to get started?
Team City is installed using windows installer. It needs java to be installed on the machine. Thus a web dashboard is used to configure a new build. The entire configuration is done by web dashboard. It has simple step by step configuration. It has both free and commercial version. For small teams and few projects free version works fine. Overall all the setup and configuration is easy.
Which source control system can be integrated out of the box?
| Source Control Name | Team City |
| AccuRev | Yes |
| Alienbrain | No |
| BitKeeper | No |
| CA Software Change Manager | No |
| ClearCase | Yes |
| CMVC | No |
| CVS | Yes |
| Darcs | No |
| Dimensions | No |
| Git | Yes |
| GNU arch | No |
| GNU Bazaar | No |
| Integrity | No |
| Mercurial | Yes |
| Perforce | Yes |
| Plastic | No |
| PVCS | No |
| Sourceanywhere | No |
| StarTeam | Yes |
| Subversion | Yes |
| Surround | No |
| Synergy | No |
| Team Concert | No |
| Team Foundation Server | Yes |
| Vault | Yes |
| Visual SourceSafe | Yes |
| Others |
What about Test coverage?
Team City has out of the box configuration with MSTest, Nunit Tests. Configurations is done using web dashboard. The configuration is straight forward.
What is the medium of build result notification?
There is multiple notifications configuration in Team City. Email is one of them. It also has a system tray notification which gives an easy way to isolate all build related notification. Since the web dashboard also shows summary of builds. It can be displayed on large screen or monitor for the development teams.
How easy can we find help to troubleshoot?
Team city is a proprietary system of Jet brains. It has product specification documentation. The entire feature present in it is well documented. It is also used widely in the community so help can be found there too.
Summary on few other categories:
| Category | Team City |
| Platform | Servlet Container |
| License | Proprietary |
| Windows Builder | MSBuild, NAnt, Visual Studio |
| Other builders | Rake, FxCop, Command Line |
| Notification | E-mail, XMPP, RSS, IDE, SysTray |
| IDE Integration | Eclipse, Visual Studio, IntelliJ IDEA, RubyMine, PyCharm, PhpStorm, WebStorm |
| Other Integration | Jetbrains Youtrack, JIRA, Bugzilla, FishEye, FindBugs, PMD, dotCover, NCover |
Read about Cruise Control .Net here.
2 thoughts on “Build Server Selection Influencing Factors Part 3”