In general TeamCity is the best choice for our self hosted CI/CD pipelines.

UI/UX is very reasonable and functional for many use cases, like developers trying to run and monitor builds, QA trying to access build links etc. Admin functionality is good for most use cases which require new user setup, adjust permissions, configure server properties etc.

Most used integrations on our side are - ability to offload artifacts to AWS S3, cloud profiles for agents, integrations with artifacts servers docker, npm etc.

Performance is pretty good for amount of configurations we have (hundreds).

Pricing is on higher side but manageable by company of our size.

Also it is relatively easy to find information about Teamcity on internet or through AI in case if you stuck with some particular problem.

I don't have comprehensive opinion about AI tools integrated into Teamcity we just trying to learn what it is about. Review collected by and hosted on G2.com.

I think biggest issue we struggle with right now is ability to scale. With so many configurations and so many builds, UI becomes quite limiting for editing complex multi-step configurations. I see a lot of duplicated configurations, many team members still not grasped meta-runner concept. To put it simply we need unified development environment/UI with ability to quickly refer/edit meta-runners and deal with configuration/steps. Today we have a lot of configurations with awful amount of duplication or some legacy ways of how they do things and there is no clear way for us to refactor this.

Also management of Cloud profile Agents pose own challenges. Since most agents start as AWS AMIs, ability to keep them updated is a challenge now. With each TC server update agent software has to be updated as well, otherwise each time Agents start they will be updating agent software which increases time of startup dramatically. Review collected by and hosted on G2.com.