TeamCity Reviews and Ratings

Use Cases and Deployment Scope

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.

Likelihood to Recommend

TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

TeamCity is well suited for small teams with several machines as it may become unstable for large projects.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

TeamCity is well suiting for building and maintaining CI/CD pipelines across multiple branches and environments where each one can have unique build processes and steps. It is straightforward to incorporate tests into the process as well. Generally speaking, it performs well and scales with the business. If you are working with a simple, single project in one environment though you might want to look elsewhere as I think TeamCity might be overkill for your needs.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

If you are going to host TeamCity in your own server, you will find that it works remarkably well

Use Cases and Deployment Scope

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.

Likelihood to Recommend

Well suited :

1. Big organizations where we need central control on builds

2. Apply rules and regulations is central

3. Yet it can be configurable on every build

4. Add different supportive tools of development to find bugs, vulnerabilities.

Not Suited :

1. Small Organizations where no more regulation needed.

2. When no addition of supportive tools required we can end up writing complex config for simple solutions

3. For Start-ups it is not suitable as require specific experienced developer to handle it.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

TeamCity scales well for small teams. We run it on a low-cost instance with several other tools, and it performs well. It has some pretty straight forward build configurations, but can be expanded with scripts and various build settings. It might be a bit overkill for a single, small project, however.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

TeamCity is perfect for what it's advertised to do. It's a great pipeline tool that offers several benefits over other tools. What it lacks in a tasteful UI but it makes up for it in functionality, ease of setup, integration with other tools, and one-click operation if set up correctly. Setting up triggers from Github or your favorite source control is very simple, and connecting it to your production deployment is just as easy.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

TeamCity is well suited for an organization using continuous integration, meaning you release code to production often, and an agile project management system. There are free versions available for small teams and enterprise versions available for large teams with many different builds.

TeamCity is probably overkill for basic e-commerce or blog website builds that do not require much development after the initial launch.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

It is vary valuable to integrate the traditional .NET , JS, Java projects because of the maturity and the features the platform offers. There's a ton of options to extend the build and deployment process because of the support for scripting it provides. The learning curve is quite easy and the product is intuitive and very natural to understand.

Use Cases and Deployment Scope

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).

Likelihood to Recommend

If requiring a CI system and you have VMs available to host it yourself, TeamCity is a great choice.