TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related to the version we were using. For instance, there were issues with agent specifications for particular build jobs and a timeout issue where jobs running longer than three hours would fail automatically.
Technical Support Lead at a computer software company with 5,001-10,000 employees
Real User
Top 10
Sep 6, 2024
The integration between Bitbucket and TeamCity could be smoother. I encountered challenges when passing data from Visual Studio to Bitbucket and TeamCity. Improved documentation or out-of-the-box connectors enhance this process.
Developer at a hospitality company with 1,001-5,000 employees
Real User
Top 5
Apr 12, 2024
I haven't faced many challenges or issues that I would like to see improved in TeamCity. As for deployment challenges, they are often tied to the specific technology being integrated with TeamCity. In my case, integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity.
It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it or to optimize it. As a user, I need some more graphical design. For example, in the other CI/CD, the whole pipeline or the whole job, you can clearly see the different types. The first job, the second job, et cetera, and you can stop whenever you want. You can stop, for example, at the second job, and you can replace the second job, so you can continue where you have stopped. However, in TeamCity, the whole build is like a whole block, and there is no way to stop. When the pipeline starts, there is no way that you can stop in the middle. You need to restart the whole thing.
The UI for this solution could be improved. New users don't find it easy to navigate. They need some level of training to understand the ins and the outs.
Owner at a computer software company with 11-50 employees
Real User
Top 20
Oct 22, 2021
One thing comes to mind, but maybe it's more of an issue on our side and not a problem with TeamCity itself. We don't have the high availability package. So I'd like our company to purchase that. So when one goes down, then we have a backup. I think we've purchased it, but we just haven't had anyone with the time to implement it. I think there was an extra cost, but we did buy it, and then I think you have to set it up in a certain way.
Harness stuck out to me due to the fact that it looked like testing and deployment was very simple and out of the box. TeamCity it definitely isn't plug and play. It's not a few clicks and you're done. It takes a bit more work. If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal. I would like it if they had a better system for copying or editing what has already been created. Right now it's either too simplistic, or you have to go through several steps just to delete something and to copy something that either does a whole copy or almost nothing. There is no in-between. You can't choose how much of something you take. I would prefer if there was more of, "okay, copy all of this, but leave out these steps." That would just make things a lot faster.
Software Developer at a tech vendor with 51-200 employees
Real User
Dec 16, 2019
Some of the configurations have room for improvement. They are partly calling another tool via the command line and the parameters on the command line are occasionally hard to use. If there was more documentation that was easier to locate, it would be helpful for users.
It will benefit this solution if they keep up to date with other CI/CD systems out there. Although I think TeamCity has everything anyone would need, and covers almost every scenario, it needs to keep evolving just to appear to be in sync with others. Also, more marketing would be helpful just to get the word out on what an amazing product TeamCity is.
Lead Engineer at a healthcare company with 10,001+ employees
Real User
Mar 20, 2018
Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone) to provide training classes to help newcomers get things up and running more quickly.
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's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related to the version we were using. For instance, there were issues with agent specifications for particular build jobs and a timeout issue where jobs running longer than three hours would fail automatically.
The integration between Bitbucket and TeamCity could be smoother. I encountered challenges when passing data from Visual Studio to Bitbucket and TeamCity. Improved documentation or out-of-the-box connectors enhance this process.
I haven't faced many challenges or issues that I would like to see improved in TeamCity. As for deployment challenges, they are often tied to the specific technology being integrated with TeamCity. In my case, integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity.
It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it or to optimize it. As a user, I need some more graphical design. For example, in the other CI/CD, the whole pipeline or the whole job, you can clearly see the different types. The first job, the second job, et cetera, and you can stop whenever you want. You can stop, for example, at the second job, and you can replace the second job, so you can continue where you have stopped. However, in TeamCity, the whole build is like a whole block, and there is no way to stop. When the pipeline starts, there is no way that you can stop in the middle. You need to restart the whole thing.
The UI for this solution could be improved. New users don't find it easy to navigate. They need some level of training to understand the ins and the outs.
One thing comes to mind, but maybe it's more of an issue on our side and not a problem with TeamCity itself. We don't have the high availability package. So I'd like our company to purchase that. So when one goes down, then we have a backup. I think we've purchased it, but we just haven't had anyone with the time to implement it. I think there was an extra cost, but we did buy it, and then I think you have to set it up in a certain way.
Harness stuck out to me due to the fact that it looked like testing and deployment was very simple and out of the box. TeamCity it definitely isn't plug and play. It's not a few clicks and you're done. It takes a bit more work. If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal. I would like it if they had a better system for copying or editing what has already been created. Right now it's either too simplistic, or you have to go through several steps just to delete something and to copy something that either does a whole copy or almost nothing. There is no in-between. You can't choose how much of something you take. I would prefer if there was more of, "okay, copy all of this, but leave out these steps." That would just make things a lot faster.
Some of the configurations have room for improvement. They are partly calling another tool via the command line and the parameters on the command line are occasionally hard to use. If there was more documentation that was easier to locate, it would be helpful for users.
It will benefit this solution if they keep up to date with other CI/CD systems out there. Although I think TeamCity has everything anyone would need, and covers almost every scenario, it needs to keep evolving just to appear to be in sync with others. Also, more marketing would be helpful just to get the word out on what an amazing product TeamCity is.
Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone) to provide training classes to help newcomers get things up and running more quickly.