TeamCity Reviews and Pricing - page 4

Try our new research platform with insights from 80,000+ expert users

Software Configuration Management ad Release Management at a financial services firm with 1,001-5,000 employees

Mar 30, 2015

Very useful for setting up build agents in a Unix platform.

What is most valuable?

Continuous integration
Build templates
Triggers
Plugins
Platform independence

How has it helped my organization?

We used do all of our product development builds using .net and Java languages. It is very useful to setup build agents in a Unix platform for all kinds of Unix builds.

What needs improvement?

Deployment functions need work.

For how long have I used the solution?

I've used it for two years.

Free Report: TeamCity Reviews and More

Learn what your peers think about TeamCity. Get advice and tips from experienced pros sharing their opinions. Updated: May 2025.

857,028 professionals have used our research since 2012.

What was my experience with deployment of the solution?

We had an issue when we customized TeamCity for deployment functions in a Windows environment using PowerShell scripting.

What do I think about the stability of the solution?

No issues encountered.

What do I think about the scalability of the solution?

No issues encountered.

How are customer service and support?

Customer Service:

Good. I would give them a 9/10.

Technical Support:

Good. I would give them a 9/10.

Which solution did I use previously and why did I switch?

No previous solution was used.

How was the initial setup?

Simple and easy to integrate with Subversion source code tool.

What about the implementation team?

We used an in-house team whose expertise was 9/10.

What other advice do I have?

It was simple and easy to use. Great features which are always customizable.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user215799Software Configuration Management ad Release Management at a financial services firm with 1,001-5,000 employees

Report as inappropriate

Jul 4, 2015

The tool has very great features for CI and CD. We can setup TeamCity for builidng applications in windows and unix environments and also can setup for deployments.

TeamCity was very easy to integrate with other build tools like Ant,Nant, Msbuild and Maven and Powershell and shell to implement the automated build and deployment process.

TeamCity Publish Artifacts feature is one of the best of its available features. Using this feature, any one can deploy the code or build directly from Teamcity to any environment(dev/testing/preprod and prod).

TeamCity was a great tool and it has no limits in customization with respective to CI and CD of any organizational SCM/Release Management process.

it_user215508 - PeerSpot reviewer

DevOps Consultant at a tech company with 51-200 employees

Mar 29, 2015

I use it to increase visibility and clarity of build and deployment activities.

What is most valuable?

There’s loads of valuable features but PowerShell Runner is invaluable.

How has it helped my organization?

It increases the visibility and clarity of build and deployment activities.

What needs improvement?

.net deployment needs improvement. Also, I'd like to see more NuGet/Octopus style features and Azure stuff.

For how long have I used the solution?

I've used it for over five years.

What was my experience with deployment of the solution?

It's all currently hand rolled in PowerShell.

What do I think about the stability of the solution?

Never ever had any stability issues.

What do I think about the scalability of the solution?

I have encountered some issues using large number of agents, and using git.

How are customer service and technical support?

Customer Service:

The agents are amongst the best available/experienced around.

Technical Support:

The agents are amongst the best available/experienced around.

Which solution did I use previously and why did I switch?

I have used Jenkins, TFS, Cruise Control .net, and GO. I switched from using Cruise Control .net as TeamCity is easier to use and displays important information very well. It also has great support for integrating to other products, from JetBrains and other vendors – Atlassian, JIRA, and Windows AD.

How was the initial setup?

It's very, very simple.

What's my experience with pricing, setup cost, and licensing?

Setup is the licence (and my contract rate).

Which other solutions did I evaluate?

I have used all leading CI tools.

What other advice do I have?

With low costs to adopt what are you waiting for?

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Free Report: TeamCity Reviews and More

Learn what your peers think about TeamCity. Get advice and tips from experienced pros sharing their opinions. Updated: May 2025.

857,028 professionals have used our research since 2012.

it_user212079 - PeerSpot reviewer

Automation Test Analyst at a non-tech company with 51-200 employees

Mar 23, 2015

It runs acceptance tests after each commit, giving quick and automatic feedback on software quality.

What is most valuable?

We're using it for CI and automating build pipelines.

How has it helped my organization?

Rerun failed tests after overnight execution, saving manual re-execution time during working hours.
Run acceptance tests after each commit, giving quick and automatic feedback on software quality.
Automate build pipeline process, removing human errors from the process itself.

What needs improvement?

Setting up build configurations involves too many steps, as the process is too much broken down. We could do with the same number of steps but less groups.

For how long have I used the solution?

I've used it for about two years.

What was my experience with deployment of the solution?

I'm not in charge of this, I have updated TeamCity once and it seemed like a quite straightforward task (but slow, due to the DB backup) once I found the online walk-through.

What do I think about the stability of the solution?

No issues.

What do I think about the scalability of the solution?

It's working perfectly with multiple projects running continuously on five build agents.

How are customer service and technical support?

Customer Service:

I've never had to use customer support.

Technical Support:

The user guide is quite thorough and extensive. Some topics are hidden a little bit, but after a while all the queries are answered.

Which solution did I use previously and why did I switch?

No previous solution was used.

How was the initial setup?

After updating TeamCity, the setup process was quite straightforward, guiding me step by step through the configuration of the new tool.

What about the implementation team?

It was an in-house implementation.

What was our ROI?

It is vital to our business to have quick and robust builds, and TeamCity is helping us to keep everything tidy and under control.

What other advice do I have?

An FAQ section with all the most common issues/most asked technical questions would be more than welcome.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Systems Administrator at Facebook

Jan 22, 2015

I generally find TeamCity a lot more intuitive than Jenkins.

Moving to TeamCity from Jenkins

At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays.

The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation.

Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident).

I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface.

One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the first parent of the merge commit and sends the e-mail to them, when in reality it’s usually the merge author that should be getting that information. Maybe I’m just ignorant of where to find a setting to change that behaviour.

Being able to jump the queue is useful when releasing. It requires a plugin to do in a sane way in Jenkins, unless you’re willing to kick everyone else out of the queue. TeamCity can do it by default, and it’s obvious how to do so when scheduling the tests.

There are supposedly more advanced features in Jenkins that don’t exist in TeamCity (yet), but I don’t think we use them.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user241605Build & DevOps Engineer; QA Automation at a healthcare company with 1,001-5,000 employees

Report as inappropriate

May 19, 2015

As usual, the answer is that there is a plugin to solve the problem: "Jenkins’ front page presents information that is simply not useful in a non-linear development environment"

Custom views allows a logged in user to see only the jobs they want to see.

Edit: and the custom views can be hard coded lists of jobs, or can be regular expressions that parse job names / labels, etc. Very flexible and very useful for large jenkins systems.

Buyer's Guide

Download our free TeamCity Report and get advice and tips from experienced pros sharing their opinions.

Updated: May 2025

Product Categories

Build Automation

Buyer's Guide

Download our free TeamCity Report and get advice and tips from experienced pros sharing their opinions.

Quick Links

Learn More:

Questions: