Likelihood to Recommend
For all continuous integration features like multi branch pipeline, continuous build, and deployment execution, highly customizable groovy scripting, well integration with most of repositories like SVN, GIT, etc. are some of the exceptional features which helps devOps related tasks a treat to work everyday. With some minor changes in agent configuration and handling of their configuration on master instances would reduce a lot of issues. Also, cache of maven handling on agents needs to be improved (though not related to tool but the CI pipelines). But, since this is a very mature and performant tool, we expect some out of the box functionalities to handle all such scenarios. Overall, the tool works wonders because of its highly customizable features.
Read full review
TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.
Read full review Pros Customer Support Solutions engineering Read full review TeamCity provides a great integration with git, especially Bitbucket. When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting. TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things. Read full review Cons File or Workspace Management Agent configurations at master level Better Support for issues in product Read full review The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations. Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious. Read full review Performance
TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.
Read full review Support Rating
Support seems very unreachable from my experience. They handle cases if developers are facing issues, support seems to be very limited. It's not like other tools in a market where every mail is being taken priority and responses are sent. We see a lack in this particular aspect when it comes to CloudBees Jenkins Platform.
Read full review Alternatives Considered
CloudBees Jenkins Support is on par with the other enterprise tools we're currently using. It has performed well enough that we've adopted the product and placed it in the critical path of our software delivery pipelines.
Read full review
TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (
) is a hosted SAAS application in Microsoft's Cloud.
is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only. TeamCity's interface is easier to use than
, and neither have a great deployment pipeline solution. But
's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
Read full review Return on Investment Positive - Handles number of requests Positive - Customizations of pipelines helps integrate many type of frameworks Negative - Cache management on agents for dependencies downloaded Positive - credential management helps reduce configurations to be done for each project job at manual level Read full review TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools. TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall. TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability. Read full review ScreenShots