TrustRadius Insights
TeamCity has proven to be an invaluable tool for software development teams across various organizations. Users have utilized TeamCity in …
Overview
What is TeamCity?
TeamCity is a continuous integration server from Czeck company JetBrains.
Recent Reviews
Reviewer Pros & Cons
Pricing
N/A
Unavailable
What is TeamCity?
TeamCity is a continuous integration server from Czeck company JetBrains.
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://www.jetbrains.com/teamcity/buy
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
Alternatives Pricing
What is Codemagic?
Codemagic is a developer's CI/CD tool for mobile app projects. Build Android, iOS, React Native, Ionic, Unity, and Flutter projects on Codemagic.Codemagic uses its own CLI tools under the hood to perform complicated tasks like code signing and distribution to the stores. These are open-sourced and…
What is Appsmith?
Appsmith is an open source framework to build admin panels, CRUD apps and workflows.
Product Demos
Sitecore CI/CD with TeamCity and TDS Demo
YouTube
Redgate DLM Demo (with TFS, TeamCity, & Octopus Deploy)
YouTube
CI/CD with JetBrains TeamCity | TeamCity Tutorial
YouTube
Demo Teamcity Build Project 2 (end)
YouTube
TeamCity Fundamental Tutorial for Beginners with Demo || Class - 01 || By Visualpath
YouTube
TeamCity demo - part 1
YouTube
Product Details
- About
- Competitors
- Tech Details
- FAQs
What is TeamCity?
A Continuous Integration and Deployment server that provides out-of-the-box test intelligence, real-time reporting on build problems, and boasts scalability. It is available both as an on-premises and a cloud-based version.
TeamCity Video
Getting Started with TeamCity
TeamCity Competitors
TeamCity Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
TeamCity is a continuous integration server from Czeck company JetBrains.
The most common users of TeamCity are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(58)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
- Recommendations
TeamCity has proven to be an invaluable tool for software development teams across various organizations. Users have utilized TeamCity in their agile project management systems, specifically within the web development team, to streamline their workflow and enhance productivity. By seamlessly integrating their git repositories with their ticketing systems, users have been able to test and release code from the development environment to the production environment with ease.
The software's automation testing capabilities have been critical for both development and product support. With TeamCity, users have been able to evaluate and integrate numerous projects, pulling together over 300 components of their SaaS-based product. This has allowed them to schedule, execute, and generate reports for various types of automation testing, ensuring the quality and reliability of their software.
One of the standout features of TeamCity is its user-friendly interface. Users have praised how easy it is to navigate and manage builds and releases within the system. Additionally, TeamCity offers flexible templates through its templates, variables, and parameterization capabilities. This enables users to create common solutions, such as deploying MVC applications to IIS, quickly and efficiently.
TeamCity seamlessly integrates with several popular platforms like Git, Azure, AWS, and Visual Studio Team Services. This integration allows development teams to leverage existing tools in their CI/CD build process without any hassle.
While users appreciate the functionality provided by TeamCity, some have expressed a desire for more comprehensive deployment visualization features. However, this minor limitation does not detract from the overall effectiveness of the software.
Overall, TeamCity has become an essential tool for development teams looking to implement continuous integration and continuous deployment practices. By providing immediate feedback on code issues and enabling thorough testing before delivery to customers, TeamCity ensures a smooth and efficient development process. Its ease of configuration and implementation also makes it suitable for small organizations with multiple projects. With its ability to meet quality expectations by running automated unit tests and handling various environments, customers find great value in using TeamCity for their software development needs.
Reliable Performance: Many users have praised the product for its reliable performance. Several reviewers have stated that the product consistently meets their expectations and performs well without any issues.
User-friendly Interface: A significant number of customers have appreciated the user-friendly interface of the product. Numerous users mentioned that the interface is intuitive and easy to navigate, making it simple for them to use and understand all its features.
Great Customer Support: Several reviewers have expressed their satisfaction with the excellent customer support provided by the company. Users have reported positive experiences while seeking assistance from customer support representatives who were helpful, knowledgeable, and prompt in resolving their queries or concerns.
Long and Manual Upgrade Process: Many users have expressed frustration with the lengthy and manual upgrade process for TeamCity. They have found it to be time-consuming and cumbersome, requiring significant effort.
Lack of SaaS-based Solution: Several reviewers have mentioned their disappointment in the lack of a SaaS-based solution for TeamCity. This means that users are required to host and maintain a large server along with multiple build agents, which can be inconvenient and resource-intensive.
Weak Pipeline Visualization: A common concern among users is the weakness of TeamCity's pipeline visualization feature. They feel that it could benefit from improvements in terms of clarity and usability, as it currently falls short compared to other aspects of the platform.
- Users recommend TeamCity over Jenkins for its additional features, ease of use, and integration capabilities.
- They highly recommend TeamCity to IT companies and suggest that it is worth the investment for enterprise continuous integration.
- Users also recommend self-hosting TeamCity for small companies and mention its value compared to other services.
- Furthermore, they recommend taking advantage of the free trial, checking available plugins, and evaluating new major versions and security risks.
- Overall, users think TeamCity is a great product for build automation and continuous integration and consider it as one of the best CI tools available.
Attribute Ratings
Reviews
(1-18 of 18)Companies can't remove reviews or game the system. Here's why
TeamCity is our primary build, test, and deploy automation tool. It is the key orchestration piece for the SDLC of more than 12 software products. TeamCity allows us to automate a number of tasks to ensure repeatable results and allows team members to spend more time developing rather than running through the manual work of testing and deploying our software solutions.
- build automation.
- Deployment automation.
- unit test automation.
- dependency chaining.
- branch management.
- The UI is getting a bit dated but has taken on a serious overhaul in recent builds.
- Build configurations as code uses a push/pull mechanism which feels a bit clunky to use.
August 16, 2021
TeamCity, a must for every team
TeamCity is used across all the development, test and DevOps departments across the company. It's integrated with every GitLab project to provide efficient continuous deployment respecting the priorities of the different projects' builds and the availability of the nodes which are multiple racks. It has been an excellent decision to purchase such a tool.
- User interface
- CD
- Pipeline
- Updates
- Customer service
August 13, 2021
TeamCity Delivers
We make use of TeamCity to build and deploy our code from our git repositories to our various environments - development, test, staging, and production. We have incorporated comprehensive tests into the process as well, making TeamCity the backbone of our CI/CD pipeline that has strengthened our ability to deliver features.
- The ability to have different build processes and monitoring per branch/environment
- Run tests as part of the CI/CD pipeline
- Status monitoring across multiple projects with build histories
- When it is time to upgrade versions it is a cumbersome and time consuming process
- Some of the reporting could be better, no real visualizations of pipelines, histories, etc.
August 12, 2021
It gives you exactly what is advertised
The organization is rather small, so it is used by the whole organization, for all the projects we are working on. We are using it to perform tasks of continuous integration and continuous deployment to several environments including test, acceptance and production.
We are also running all our automated unit tests using TeamCity.
We are also running all our automated unit tests using TeamCity.
- continuos integration
- continuos deployment
- running tests
- highly configurable
- fast when using several workers
- the UI can be improved
TeamCity is being used across my company. We have integrated TeamCity with the CI/CD pipeline. This is solving number of problems which occur if we do not have CI/CD in place. Configuring node servers to build the projects is easy. We can easily configure the properties while building the specific branch. Can easily build multiple feature/develop/release branches at once. It gives all build related information at one place, so can troubleshoot problem in build easily. Basic implementation of application is easy.
- Selection of build server for specific build
- We can add configurable properties
- One stop solution to create deployable package
- Initial and basic setup is easy
- It is not plug and play thing
- Need more specific configurations for smaller projects as well
- Online help is less available
- Basic implementation is easy but I think feature add on can be complex as it involve some language knowledge as well.
We use TeamCity on a self-hosted instance to build our ASP.NET projects, .NET desktop projects, and Angular projects. We use it to automatically build these various projects from our git repos and then execute deployment scripts via Octopus Deploy. We also run unit tests on each build and tie in build and test status to our code review tool, Upsource. TeamCity is part of our end-to-end pipeline that allows us to get quality changes out the door quickly and react to production issues quickly.
- See build status across many projects.
- It monitors multiple branches with different build processes for each.
- It's a useful unit test runner with test history and identification of flaky or problematic tests.
- Reading build output logs can be a pain at times, as they aren't really parsed; just long lines of output.
- When you have multiple projects and branches, determining what is currently building, what is pending, and what has failed can be difficult.
May 07, 2019
TeamCity above all else
We use TeamCity as a CI/CD tool for our pre-production and production builds. We've set it up for near full automation use and have set it up with multiple steps for each build. TeamCity is used on a team-by-team basis here at my work. Several surrounding teams in many different departments use it with much success. TeamCity solves the problem of integrating other tools in the CI/CD build process without being too complicated or without too much overhead. Given a corporate firewall can cause great limitations, it's nice to have a tool that's simple to integrate with other tools.
- Build Automation: easy setup, one-click deployment, reliable use, great documentation/instruction.
- Tool Integration: great documentation, several existing examples, easy setup.
- Step tracking: clear pipeline display, easy to locate build logs, clear error messages.
- Desktop app: TeamCity is browser-based, and some may prefer having a desktop application to view deployments on.
- Tasteful UI: TeamCity has a simple, non-graphic UI that some may find boring or not as intriguing as some of the other options.
TeamCity was used by the technology department of the organization, especially by the web development team.
We used TeamCity to test and release code from our development environment to our production environment. Our web developers worked under an agile project management system and used continuous integration. In this system, TeamCity allowed us to integrate our git repository with our ticketing system, as well as help us quality assure and properly release clean code to production.
We used TeamCity to test and release code from our development environment to our production environment. Our web developers worked under an agile project management system and used continuous integration. In this system, TeamCity allowed us to integrate our git repository with our ticketing system, as well as help us quality assure and properly release clean code to production.
- TeamCity provides a great integration with git, especially Bitbucket.
- When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
- TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.
- Upgrading TeamCity is a long and manual process.
- Java skills are needed to fully utilize TeamCity, although they are not necessary for basic or medium-level use.
August 03, 2018
My experience with TeamCity
TeamCity is the go-to tool to getting the Builds and Deployments packages for a variety of platforms like .NET, Java and JS etc. It is being used by the whole organization. It unifies the build and deployments needs of all the diverse projects to a single platform and solves the build and release issues previously we faced and reduces the time to go to Prod.
- First and foremost is the ease of use
- Very good support for extending , plugging and scripting support to customize your needs
- Lightweight and accessible by browser.
- The Debug log is quite verbose and could be made more intuitive for troubleshooting build errors
- I would recommend improving it by some kind of integration with platforms like StackOverflow to aid developers and further improve the turnaround time for setting up successful builds
- There is still scope for improvement for build integration with projects in AWS and Azure cloud platforms.
May 25, 2018
TeamCity 7 Years On!
Our company has two products. 1 of which, TeamCity is the critical tool for development and for both products, it's the critical tool for automation testing. In all cases, both development and product support use it. It's the tool which pulls together the 300+ components that make up our current SaaS-based product and the tool which schedules, executes and produces reports for all our type of automation testing (behavioral, backward compatibility, performance, security, and load).
- A very friendly UI with good drill-down and "Pro" capabilities compared to all other CI systems
- A good reporting system that allows all our different types of automation tests to produce output for
- Fantastically simple to setup and configure
- The biggest and only issue we have is the lack of a SaaS-based TeamCity solution. Currently, we have to host and maintain 1 big TeamCity server and up to 15 build agents to build our 1500+ builds
We used TeamCity as our Core Continuous Integration solution for four years. I love TeamCity's easy to use interface, and the way builds and releases are linked together in dependency Chains. I found it particularly helpful that Builds can be run separately, or in advance of Releases - and then when Releases are run the Builds only run again if the code has changed. TeamCity's Templates, Variables, and Parameterization capabilities also made it very easy to establish a flexible template for common solutions such as deploying MVC applications to IIS. Once templates were configured I could create a "build and release" for a new project in less than 10 minutes.
While TeamCity has a simple to use and understand chaining mechanism, allowing builds to call "builds and releases" to rely on multiple dependency chains - TeamCity's PipeLine visualization capabilities are one of its weakest points. I had a complex build across five different environments consisting of eight different solutions and over 20 deployment targets. During a major update, it would have been nice to visualize the deployment pipeline and "watch" the deployment process for issues - but that really isn't possible with TeamCity. Outside of that, TeamCity worked great, integrated well with all of our platforms: Git, Azure, AWS, Visual Studio Team Services.
Great Product.
While TeamCity has a simple to use and understand chaining mechanism, allowing builds to call "builds and releases" to rely on multiple dependency chains - TeamCity's PipeLine visualization capabilities are one of its weakest points. I had a complex build across five different environments consisting of eight different solutions and over 20 deployment targets. During a major update, it would have been nice to visualize the deployment pipeline and "watch" the deployment process for issues - but that really isn't possible with TeamCity. Outside of that, TeamCity worked great, integrated well with all of our platforms: Git, Azure, AWS, Visual Studio Team Services.
Great Product.
- Build: Parameterization, Chaining from multiple sources, Templates, and general ease of use.
- Release: Works extremely well with "Build" process.
- Updates and Upgrades are simple, effective, and reliable.
- Pipeline Visualization: TeamCity's weakest area
TC is used across our organization to do builds for all our apps and services. We started using it to replace our custom build and deploy system because we needed something more flexible and customizable, and something that did not need a fully dedicated support team.
- Fully customizable build process. Each step of the build process can be parameterized and customized to address specific needs of particular applications. This allowed us to easily convert from a custom VM-based environment to our current Docker-based environment.
- Manages large numbers of build agents seamlessly. This allows us to run multiple builds on many different applications in a most efficient manner.
- Build steps can be managed in an arbitrary manner, allowing some parts of the process to proceed in parallel while restricting others to depend on completion of all relevant steps.
- The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
- Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.
October 25, 2017
Build with Confidence!
We use TeamCity for Continuous Integration & Delivery of our software products. We have many projects for various customers that are built and integrated continuously whenever we check code into our git repositories.
We use a mixture of Gradle & Maven builds and TeamCity handles both well.
We get immediate feedback from TeamCity if a code change has caused issues with other linked projects and, because we have confidence in our tests we also have confidence in a 'green' build prior to delivery to a customer.
We use a mixture of Gradle & Maven builds and TeamCity handles both well.
We get immediate feedback from TeamCity if a code change has caused issues with other linked projects and, because we have confidence in our tests we also have confidence in a 'green' build prior to delivery to a customer.
- Easy to set up. The UI is pretty easy to navigate and use. You can have your project up and running in minutes.
- Good integration with various build frameworks/methodologies. You can run standard Maven, Ant or Gradle builds with virtually no customization.
- Decent support for extensions via the plug-in mechanism. You can integrate with other popular tools such as Artifactory via plug-ins. Or write your own.
- Upgrade process can be a bit of a pain - have to do this manually on your server.
- It's easy for the new user to get lost in the UI. Although this is true for most systems that offer such a wide range of configuration options.
June 23, 2017
If you practice TDD, get TeamCity!
TeamCity is used in every rollout of code to production in engineering. We heavily believe in test driven development, we probably have more tests than actual code for the product. Since we have nightly releases, TeamCity (CI) is great for getting all our builds tested and ready to go for release.
- GitHub integration is invaluable.
- Decent UI that allows many tasks to be performed with just a click.
- Detailed failure messaging, stack traces.
- There can be a lot of info to display so the UI can be a bit cluttered, especially if you have a lot of builds/apps going at once.
- Needs more intuitive way to kick off tasks or just even access settings.
- The detail of stack traces is nice, but it would be even better if it was cleaned up more and displayed in a better human-readable format.
April 14, 2017
TeamCity - My Go-To Build system
I set up TeamCity for our core product continuous integration. For both the main product and the core libraries it is used to compile on check in, build and deploy on pull requests, and to run the unit and functional tests. No code goes into the develop or main branches without passing through this process.
- Ease of configuration. Some build systems are difficult to get started on. TeamCity can be up and running quickly.
- Cross platform. TeamCity runs on most configurations, and a master can configure agents of other OS types, so it can build nearly anything.
- Price. It's free for limited use, so you don't need to pay until you ramp up and are using it a lot.
- The upgrade process could be smoother. Moving from one major version to another involves jumping onto all your servers and often causes some pain.
- Log formatting could be a little clearer, though that is true for almost all build systems.
March 31, 2017
TeamCity for the Win!
We use TeamCity at San Diego State Instructional Technology Services to support our CI (Continuous Integration) and CD (Continuous Deployment) needs to support our Agile DevOps practices we implement for our developers. TeamCity also allows us to integrate with our Issue Tracker (YouTrack) and GitHub to ensure we stay on top of issues, and make sure that all of our production deployments are stable and reliable (thanks to Unit Testing, which is handled automatically by TeamCity on artifact build and deploy).
- TeamCity (via a Plugin) allows us to deploy directly to our Tomcat Staging Server, and via a different plugin, allows us to interface with our Docker Container to do a Zero Downtime deployment to our production system.
- TeamCity notifies the committing developer, as well as the project lead, if and when a build fails and for what reason.
- The User interface of TeamCity is also very intuitive and easy to understand.
- TeamCity's base plan is somewhat limited in regard to the number of projects, specifically build configurations, that you can have.
- It can take a little bit to get used to the Project Hierarchy structure of TeamCity, however, once understood, it can be extremely powerful for sharing properties and components between projects.
Every single commit to our codebase results in an automatic full build and unit test run, then this code is automatically deployed to a bare-bones environment if it builds and the tests pass.
- Visual Studio integration is extremely tight.
- Supports a wide variety of test runners, first-class languages, and source control systems out of the box, and even more with plugins.
- The configuration system allows our build engineers to reuse build configurations and configuration components, the same way our developers reuse code.
- The entire thing is built in Java. Not a dealbreaker, but this does mean you need to know Java if you want to create a plugin for something TeamCity doesn't do natively.
- TeamCity does not seem to have any HA functionality, so no clustering, no active/passive. If your functional CI server dies, your build pipeline dies.
May 03, 2016
A easy and clean continuous evaluation tool.
Score 9 out of 10
Vetted Review
Verified User
TeamCity was used by my team to do the continuous evaluation and integration of various projects under our team. It was used by our team only in our organisation. It was easy to spot wrong commits and build a failure before the product release. This was very easy with the help of a continuous integration tool like TeamCity that has a very versatile UI.
- By default, the TeamCity installation comes with embedded Hypersonic SQL DB (HSQLDB for short). It is a good database in its own right and has its strengths in the situations where you would need a fast and tightly integrated in-process DBMS embedded into your Java application. But running a production server on HSQLDB is risky.
- TeamCity offers much better security than Jenkins from out of box installation itself.
- Browser-hosted interface serves as the primary way to administer TeamCity users, agents, projects, and build configurations. It provides project status and reporting information suitable for a broad range of users and project stakeholders. It provides build progress, drill down detail, and history information on the projects and configurations.
- In TeamCity a single branch can be built dynamically. When configuring a Git or Mercurial VCS root, you need to specify the branch name to be used as the default.
- TeamCity download was about 535 MB. Starting up TeamCity server on Mac is quite a large space.
- When compared with the existing continuous integration tools the number of plug-ins available is much less for TeamCity.