Every enterprise business uses this tool for maintaining their services enabled and establish the best business flow. All the services that are being build via Mule can be available via team city to be deployed.Its features include build history, user management and system maintenance. Build history has excellent feature of holding the various build version that are deployed earlier.Use service messages in your build scripts, interact via REST API, or create plugins for TeamCity using Open API. User Management has different ways of user authentication, and a log with all user actions for the transparency which can be used for tracking all activity on the server.Best feature is Version Control System(VCS) in which Team city in a single build it can take source code from different VCS Repositories.All the versions history is available environmental wise.

The least of this software is there are some additional features required for the versions to avail across different enviroments like manual build configurations process can be avoided for the lower environments and UI part can be increased looking for new enhancements

I am able to successfully manage over 600 projects in Teamcity in my environment. Updates are a breeze and downtime has been damn near zero in the five or six years I've used this product. The build configs are super flexible however I've not used another product so I'm not sure how my experience compares to the next.

I'm not a huge fan of the experimental UI for some views but for other items I prefer it. I'm often switching back and forth between the two UIs

It connects well with other JetBrains tools.

It is not as popular as Jenkins so does not have as many plugins and the community using it is a lot smaller.

It does its job, and once you've set it up it's pretty solid. Agents and server have never needed a reboot as far as I know, and upgrades are quick enough. The integration with the VCS (SVN where I work) can let you keep track of what you have down the pipeline and, if you use the right tracking tool and add ticket numbers to the commit comments, you might find useful seeing what brought to that commit. If you often create new projects, the template feature can enormously speed up the process.

It's very very easy to screw up. It gives you quite enough rope to hang yourself and your whole team twice, like creating dependencies among builds so that a simple commit can make the agents run for hours, or other amenities where you're not really sure what's the code you're building from (or, you might even be sure, but wrong!) If you're not well organized and don't know your way around the myriads of configurations, you may well end up not knowing what features you are deploying. It really needs some serious study before using it in production, and since it's not something you configure everyday, it's not easy to keep trained. In this perspective, the template feature will make you forget what's going on. Sadly, it's the only CI/CD tool I've ever used, so I can't compare it to anything else.

TeamCity By JetBrains provide the hassle free Continuous Integration & Delivery. The freeware license come with up to 100 build configuration and 3 build agent are enough to check the feasibility study of your product. The powerful build CI & smart configuration make it enterprise like DevOps tool.

TeamCity by JetBrains is one of the best and simple tool to manage the build and Integration. The powerful integration features out of the box make it unique and operation team first choice. The DevOps approach helps in continuous Integration & Delivery. Smart Configuration feature like project hierarchy, in-build templates, build chains & dependencies split the build sequence in multiple step to serve in simplex form. The Version Control Systems integrate the process in comprehensive way. Build History is also helpful in tracking the issue & let us allow in tracking the changes in the development process. Statistics of build history and test result help in generating the reports.

There are numbers of In-build configuration plugins for cloud integrations like Amazon, Azure, vSphere, Kubernetes and many more but cluster and creating the plugin for on-premises infrastructures is really a big and complex task to do with the TeamCity without the help of expertise.