What is our primary use case?
We have different projects on TeamCity. Mainly, for example, I use it to automate our build. We have scripts that need to be run on schedule to do some scanning of our codes to detect vulnerabilities and so on. I have, for example, a build that decorates the script and launches it every Sunday night, so we can have our reports by Monday, so our managers can see them, and we can discuss them.
We also use it to deploy our infrastructure as code in the environment and to execute that or deploy that to the dev environment. We have many builds that deploy our code in the dev environment.
What is most valuable?
TeamCity is a very user-friendly tool. I didn't know about it five months ago, and I started digging into it. To be honest, it was very easy to start on it and to build my first build and to understand the concept or the methodology internally.
It's very easy to configure as well. You can configure your build and the steps within in it in a very easy way since you can choose the syntax with how you will write your code. In comparison with Gitlab, Gitlab has its specific syntax, so you need to learn that; however, with TeamCity, you have the choice to choose the framework you want and so you can start easily.
What needs improvement?
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.
For how long have I used the solution?
It's been five to six months, maybe, since I started using the solution.
What do I think about the stability of the solution?
The solution works quickly, and I haven't noticed any issues with stability; however, I haven't tried to test it out either.
What do I think about the scalability of the solution?
The whole IT department is using TeamCity. That's 40 to 50 people, approximately. Every dev and every DevOps person is using TeamCity.
How are customer service and support?
I've never contacted technical support.
Which solution did I use previously and why did I switch?
How was the initial setup?
It's easy to set up. I did it on my local machine, not on our real server, and it took me a couple of minutes. Since it's an online application, we can deploy it in just a minute and just with a few clicks. It's not that complicated.
What's my experience with pricing, setup cost, and licensing?
It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without you being involved and having it and managed by them, there may be costs involved. That's the paid feature.
Which other solutions did I evaluate?
I was not involved in evaluating other options or choosing this solution.
What other advice do I have?
I'm a customer and end-user.
We're using the latest version of the solution.
It's a great solution. I only wish they spent more time working on the graphical part. It would be nicer and more focused if they did.
I'd rate it seven out of ten as it is easy to start with, and it's not complicated to deploy in your on-premises deployment.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
