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.
We're just a customer. We're using the most up to date version of the solution currently. TeamCity is our main continuous integration tool, however, it is deployments that we were looking into improving. With Harness I saw that the deployment process was very polished. And at this point I was wondering if there was any interactivity between the two solutions, or just what would be the benefits of just switching completely to Harness. We're currently researching that now. I'd advise other organizations to do a lot of research before you begin creating anything. The solution needs a lot of maintenance in the sense that you need to understand all the different pieces. You need to be able to look at the servers and the agents, and, if you're going to implement anything new, you'll need to understand it is going to take a while to get it right. I'd rate the solution eight out of ten.
Software Developer at a tech vendor with 51-200 employees
Real User
2019-12-16T08:14:00Z
Dec 16, 2019
We use the on-premises deployment model. I'd advise others that it's absolutely necessary to use an integration tool that can run integration tests. I'd rate the solution eight out of ten.
Lead Engineer at a healthcare company with 10,001+ employees
Real User
2018-03-20T14:54:00Z
Mar 20, 2018
Wish the Tomcat server could magically convert to HTTPS (instead of the apparent default of HTTP). There are published works on using TeamCity (separate works by authors Melymuka and Mahlingam, both on Packt Publishing), however both of these are out of date which makes the initial learning curve more challenging. I invite these publishers to update their work; would gladly purchase updated revision.
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.
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.
I would rate this solution a nine out of ten.
I rate TeamCity eight out of 10.
We're just a customer. We're using the most up to date version of the solution currently. TeamCity is our main continuous integration tool, however, it is deployments that we were looking into improving. With Harness I saw that the deployment process was very polished. And at this point I was wondering if there was any interactivity between the two solutions, or just what would be the benefits of just switching completely to Harness. We're currently researching that now. I'd advise other organizations to do a lot of research before you begin creating anything. The solution needs a lot of maintenance in the sense that you need to understand all the different pieces. You need to be able to look at the servers and the agents, and, if you're going to implement anything new, you'll need to understand it is going to take a while to get it right. I'd rate the solution eight out of ten.
We use the on-premises deployment model. I'd advise others that it's absolutely necessary to use an integration tool that can run integration tests. I'd rate the solution eight out of ten.
Wish the Tomcat server could magically convert to HTTPS (instead of the apparent default of HTTP). There are published works on using TeamCity (separate works by authors Melymuka and Mahlingam, both on Packt Publishing), however both of these are out of date which makes the initial learning curve more challenging. I invite these publishers to update their work; would gladly purchase updated revision.