TeamCity logo


TeamCity is an ultimate Continuous Integration tool for professionals
+ 1

What is TeamCity?

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
TeamCity is a tool in the Continuous Integration category of a tech stack.

Who uses TeamCity?

254 companies reportedly use TeamCity in their tech stacks, including Accenture, ebay, and Stack Overflow.

529 developers on StackShare have stated that they use TeamCity.

TeamCity Integrations

Slack, Datadog, BrowserStack, SonarQube, and Sauce Labs are some of the popular tools that integrate with TeamCity. Here's a list of all 33 tools that integrate with TeamCity.
Public Decisions about TeamCity

Here are some stack decisions, common use cases and reviews by companies and developers who chose TeamCity in their tech stack.

Tymoteusz Paul
Devops guy at X20X Development LTD | 21 upvotes 路 3.6M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Shared insights

TeamCity builds then copies to each web tier via a powershell script. The steps for each server are:

  • Tell HAProxy to take the server out of rotation via a POST
  • Delay to let IIS finish current requests (~5 sec)
  • Stop the website (via the same PSSession for all the following)
  • Robocopy files
  • Start the website
  • Re-enable in HAProxy via another POST TeamCity
See more
Mihai Ciureanu
Head of Technology at Wecheer | 1 upvotes 路 13.4K views
Shared insights

We use TeamCity because it is one of the most user friendly CI/CD servers, and it's also FREE for up to 100 build configurations, basically supporting a startup until it grows significantly. Integration with dotnet core tools is also excellent making things easier for us.

See more
Shared insights

TeamCity is our main continuous integration server. It starts creating builds and running tests based on commits that we make in our hosted bitbucket repositories. From there, we have a set of configuraitons that can deploy the built and tested artifacts (web app, batches, db, etc...) to a stage or production server. We still release manually, but we release often, and TeamCity has nice features to help us roll back when things don't work out as planned. TeamCity

See more
Sascha Manns
Shared insights

I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration. TeamCity

See more
Malvern Kamukondiwa
Web Solutions Architect at Adthena | 1 upvotes 路 10.8K views
Shared insights

We use TeamCity because it allows us to #automate our #ContinuousIntegration and deployment pipelines. We can focus on delivery and quality and eliminate as many manual tasks as possible.

See more

TeamCity's Features

  • Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
  • Simplified setup: create projects from just a VCS repository URL
  • Run multiple builds and tests under different configurations and platforms simultaneously
  • Make sure your team sustains an uninterrupted workflow with the help of Pretested commits and Personal builds
  • Have build history insight with customizable statistics on build duration, success rate, code quality, and custom metrics
  • Enable cost-effective on-demand build infrastructure scaling thanks to tight integration with Amazon EC2
  • Easily extend TeamCity functionality and add new integrations using Java API
  • Great visual project representation. Track any changes made by any user in the system, filter projects and choose style of visual change status representation

TeamCity Alternatives & Comparisons

What are some alternatives to TeamCity?
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.
It monitors the execution of repeated jobs, such as building a software project or jobs run by cron. Among those things, currently it focuses on the two jobs
Octopus Deploy
Octopus Deploy helps teams to manage releases, automate deployments, and operate applications with automated runbooks. It's free for small teams.
With FinalBuilder you don't need to edit xml, or write scripts. Visually define and debug your build scripts, then schedule them with windows scheduler, or integrate them with Continua CI, Jenkins or any other CI Server.
See all alternatives

TeamCity's Followers
742 developers follow TeamCity to keep up with related blogs and decisions.