While TeamCity serves its purpose for small projects or teams that don't require a multi-vendor tool, for larger setups, enhanced features could be beneficial.
Technical Support Lead at a computer software company with 5,001-10,000 employees
Real User
Top 10
Sep 6, 2024
I utilize feature branches for version control, merging them into the main branch only after thorough testing. During integration with Bitbucket, TeamCity fetches the specific branch for deployment, ensuring that only stable versions are deployed. This process minimizes conflicts and ensures a smooth deployment to production environments. We typically set up automated notifications for build and deployment statuses. For instance, I configure notifications for successful and failed builds sent to our Slack channel or via email. We also integrate continuous monitoring tools like New Relic or Datadog to provide real-time post-deployment feedback on deployments and application performance. Any issues identified through these tools are quickly addressed through rollbacks or patches. We primarily relied on existing configurations and custom parameters, which reduced the necessity for manual scripting. Nevertheless, I have automated testing scripts, backup processes, and deployment steps in other tools to ensure smooth and repeatable deployments. I stay informed by reading industry blogs, attending webinars, and participating in community forums. Platforms like Stack Overflow, Reddit, and specific CI/CD tool communities provide valuable insights into new features, troubleshooting tips, and best practices. Furthermore, I prioritize experimenting with new tools and updates in a sandbox environment before introducing them into a production workflow. Collaboration is essential for a successful CI/CD process. I typically utilize communication tools like Slack and project management platforms like Jira to keep all team members aligned. Regular stand-up meetings, retrospectives, and post-mortem analyses are crucial to ensure the development, operations, and testing teams are coordinated and harmonious. Automation also allows everyone to view real-time deployment statuses and test results, promptly resolving any issues. Overall, I rate the product a five out of ten.
Developer at a hospitality company with 1,001-5,000 employees
Real User
Top 20
Apr 12, 2024
My overall rating for TeamCity is a 6, but I acknowledge that this rating is based on my limited experience with the tool. I haven't delved deeply into its functionalities or compared it extensively with other automation tools, which is why I consider it an average rating for now.
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
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
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 offers flexibility in creating build pipelines with cross-platform support, powerful plugins like Octopus Deploy, and integration with version control systems, providing a centralized automation solution for continuous integration and deployments.TeamCity streamlines CI/CD processes by supporting cross-platform building and testing for .NET, Java, and Ruby on Rails. It integrates with GitHub for code management and enables build environments for C/C++ projects, ensuring automated...
While TeamCity serves its purpose for small projects or teams that don't require a multi-vendor tool, for larger setups, enhanced features could be beneficial.
I utilize feature branches for version control, merging them into the main branch only after thorough testing. During integration with Bitbucket, TeamCity fetches the specific branch for deployment, ensuring that only stable versions are deployed. This process minimizes conflicts and ensures a smooth deployment to production environments. We typically set up automated notifications for build and deployment statuses. For instance, I configure notifications for successful and failed builds sent to our Slack channel or via email. We also integrate continuous monitoring tools like New Relic or Datadog to provide real-time post-deployment feedback on deployments and application performance. Any issues identified through these tools are quickly addressed through rollbacks or patches. We primarily relied on existing configurations and custom parameters, which reduced the necessity for manual scripting. Nevertheless, I have automated testing scripts, backup processes, and deployment steps in other tools to ensure smooth and repeatable deployments. I stay informed by reading industry blogs, attending webinars, and participating in community forums. Platforms like Stack Overflow, Reddit, and specific CI/CD tool communities provide valuable insights into new features, troubleshooting tips, and best practices. Furthermore, I prioritize experimenting with new tools and updates in a sandbox environment before introducing them into a production workflow. Collaboration is essential for a successful CI/CD process. I typically utilize communication tools like Slack and project management platforms like Jira to keep all team members aligned. Regular stand-up meetings, retrospectives, and post-mortem analyses are crucial to ensure the development, operations, and testing teams are coordinated and harmonious. Automation also allows everyone to view real-time deployment statuses and test results, promptly resolving any issues. Overall, I rate the product a five out of ten.
My overall rating for TeamCity is a 6, but I acknowledge that this rating is based on my limited experience with the tool. I haven't delved deeply into its functionalities or compared it extensively with other automation tools, which is why I consider it an average rating for now.
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.