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.

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. 

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.

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.

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.

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.

More build runners and more options are needed, although I have no worries they keep improving.

The UI could be more structured, as it is so customisable it is quite easy to get lost around the screens.

This product lacks real reporting for all the information it captures; we should be able to create reports or dashboards for management.

The product captures a lot of information about build processes, but there is no easy way to create/generate reports that can be used by management.

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.

We would like to see better integration with other version controls, since we encountered difficulty when this was first attempted. This meant that we had to use predefined scripts that we wrote on our own.

When it comes to other source control tools , such as GitHub, it's really straightforward and easy to do.

The upgrade process could be smoother. Upgrading major versions can often cause some pain.

Deployment functions need work.

Setting up build configurations involves too many steps, as the process is too much broken down. We could do with the same number of steps but less groups.

Features I would like to see in TeamCity:
Allow for shared resource locks across multiple build configurations (i.e. deploy then run integration tests against the same environment).

Allow shared resource locks to accept parameters for dynamic assignment of locks.

• Client side load as projects/builds with a lot of test history, and branches can take quite a bit of time to load
• It would also be nice to have a conditional build step: https://youtrack.jetbrains.com/issue/TW-17939
• Having project templates

.net deployment needs improvement. Also, I'd like to see more NuGet/Octopus style features and Azure stuff.

It'd be great to see future built-in support for Octopus Deploy. Currently, Octopus Deploy provides a plug-in for TeamCity, but the installation is manual, and requires a restart of the TeamCity service in order to complete the installation. This is really the only small improvement I would recommend, but it's obviously not a deal-breaker.

Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted. Whether to present an error code or just throw an exception, it was unclear, as well as having to paste a script versus executing a PS file. Fewer "options" in this section with greater consolidation and handling would be appreciated.

REST API support lacks many features in customization of builds, jobs, and settings. 

Also, integration with newer technologies needs improvement.

I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.

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.