TeamCity Valuable Features

Steven Gomez
Lead Engineer at bioMerieux, Inc.
TeamCity has a remote build feature that we have used to support legacy products (that use compilers that cannot run on current OS versions). Rather than having developers locked into an outdated PC for legacy support, we now only need to support a single VM that is configured as the build agent for the legacy product. TeamCity provides integrations for Eclipse, but in our case, it worked better to create a Python script that provided the necessary interaction between SlickEdit and TeamCity. Developers can make code changes on a current Windows or Linux system, and changes made locally are pushed to the build agent as a personal build. We are also exploring capabilities of use of the "Report Tabs". To ultimatly support FDA compliance concerns, I have a prototype of an HTML report being generated that includes CRCs, SCM URLs, SCM Revisions, etc for all items of a build chain. View full review »
Alison Monteith
Snr. Devops Engineer at Deem
The most valuable features are: * Build chains - it's really easy to set up all of your build dependencies * Snapshot dependencies and triggers - you always build the correct code as a snapshot is taken at the moment you run the build chain (i.e. no unexpected check-ins are included in your build!) * Templates - for setting standards and making the configuration easy and clean * Meta runners - sharing code TeamCity is very stable, is easy to set up and maintain. Once everything is configured there is almost zero time needed to maintain it. View full review »
RalfRosen
Software Developer at a tech vendor with 51-200 employees
The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications. View full review »
Find out what your peers are saying about JetBrains, Jenkins, Atlassian and others in Build Automation. Updated: March 2020.
407,096 professionals have used our research since 2012.