TeamCity Archived Reviews (More than two years old)

Filter by:Reset all filters
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Release and deployment process manager at a energy/utilities company with 1,001-5,000 employees
Jan 11 2016

What is most valuable?

* Centralized build automation * Ability to embed powershell scripts for automated deployments * Auditability of builds * Unit tests * Smoke tests * Automated deployments

How has it helped my organization?

Continuous integration has reduced build failures and highlighted issues sooner. Automated deployments of web services, database scripts and applications chained across all environments has minimized… more»

What's my experience with pricing, setup cost, and licensing?

The initial cost was only the cost of a virtual server, and database which was less than 1000 Euros a month. I am not aware of ongoing costs.

Which solution did I use previously and why did I switch?

We previously used Jenkins and Cruise control. We changed to enable one common solution and standard support model, also better functionality.

What other advice do I have?

Make sure you define the standards and naming conventions prior to implementing TeamCity.

Which other solutions did I evaluate?

No other options were evaluated.
Systems Administrator at Facebook
Jan 22 2015

What do you think of TeamCity?

Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far…

What is TeamCity?

TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

TeamCity customers

Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia

Download our free Build Automation Report and find out what your peers are saying about JetBrains, Jenkins, Atlassian, and more!