A easy and clean continuous evaluation tool.
May 03, 2016

A easy and clean continuous evaluation tool.

Aliya Shareef | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with TeamCity

TeamCity was used by my team to do the continuous evaluation and integration of various projects under our team. It was used by our team only in our organisation. It was easy to spot wrong commits and build a failure before the product release. This was very easy with the help of a continuous integration tool like TeamCity that has a very versatile UI.
  • By default, the TeamCity installation comes with embedded Hypersonic SQL DB (HSQLDB for short). It is a good database in its own right and has its strengths in the situations where you would need a fast and tightly integrated in-process DBMS embedded into your Java application. But running a production server on HSQLDB is risky.
  • TeamCity offers much better security than Jenkins from out of box installation itself.
  • Browser-hosted interface serves as the primary way to administer TeamCity users, agents, projects, and build configurations. It provides project status and reporting information suitable for a broad range of users and project stakeholders. It provides build progress, drill down detail, and history information on the projects and configurations.
  • In TeamCity a single branch can be built dynamically. When configuring a Git or Mercurial VCS root, you need to specify the branch name to be used as the default.
  • TeamCity download was about 535 MB. Starting up TeamCity server on Mac is quite a large space.
  • When compared with the existing continuous integration tools the number of plug-ins available is much less for TeamCity.
  • TeamCity provides continuous integration, automated build and continuous deployment for a price. When compared with the pioneers in CI field, which are free software, TeamCity is effective because the implementation, familiarisation and integration time is less.
  • Effective hours to manage this tool is less, which increases the return on investment. But we have to pay while using for bigger number of projects is a drawback when there is free softwares in the market.
  • Easy implementation.
  • Cleaner dashboard and UI.
  • Better documentation and tutorials.
They have better documentation and tutorials, a cleaner UI and dashboard and the easiest implementation. When a big team was working in the same repository we had to build every commit automatically and validate each committer and with TeamCity. The integration process was easy and it gave individual validation for individual committers.