TeamCity Reviews & Product Details


What is TeamCity?

TeamCity will make sure your software gets built, tested, and deployed, and you get notified about that appropriately, in any way you choose. It’s a continuous integration and deployment server from JetBrains which takes moments to set up, shows your build results on-the-fly, and works out of the box. And best of all – it’s free by default.

Write a Review

TeamCity Screenshots


TeamCity Profile Details

TeamCity Profile Details

Related Links
Q&A
Languages Supported
English
Vendor
JetBrains
Description
JetBrains builds productivity software for developers who want to focus more on what they want to accomplish, and less on mundane, repetitive tasks.
Company Website
Year Founded
2000
HQ Location
Prague, Czech Republic
LinkedIn® Page
www.linkedin.com
Employees on LinkedIn®
740
Twitter
@jetbrains
Twitter Followers
103,574
Show moreShow fewer

Companies Using TeamCity

Salesforce
Xerox
LinkedIn
Accenture
Hewlett-Packard
Twitter
Siemens
Nike
EMC
Apple
Intel
T-Mobile

TeamCity Reviews

Filter Reviews
Filter Reviews
Sort by
Ratings
Company Size
User Role
For Category
All Industries
Region
Write a Review
1-25 of 55 total TeamCity reviews

TeamCity Reviews

Write a Review
Filter By
Connections
Show reviews that mention
1-25 of 55 total TeamCity reviews
Copy Review URL
Assistant Project Manager
Gambling & Casinos
Mid-Market
(201-500 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"JET BRAINS again the best"

What do you like best?

I'm a fan of programs from developer "JET BRAINS", so I decided to try TeamCity. At once I will say that I was not disappointed. It has a clear user interface and good navigation on it. The platform is quite flexible and stands up for all your needs. TeamCity provides a good set of functions for a building of your project. Also you can control assembling the project and then test it. An excellent user guide, it is complete and understandable. Excellent acceptance tests, most of all I use them.

What do you dislike?

Quite a complex system. Many settings for each project, this requires a lot of knowledge and time. It would be nice to simplify and automate this process.

Recommendations to others considering the product:

TeamCity is definitely worth your attention if you are looking for an enterprise software for continuous integration. You can try it and decide yourself!

What problems are you solving with the product? What benefits have you realized?

We began to save a lot of time. We have reduced the number of failures and problems. We control about 20 projects using TeamCity. It's pretty easy to control so many projects because you can call up the necessary tests and just wait for notifications.

Copy Review URL
Social Media Manager
Restaurants
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Fantastic software product!"

What do you like best?

Teamcity is a powerful tool for continuous integration and continuous deployment in a production environment. It provides a simple setup process, with the ability to configure many parameters. The software product has a simple user interface. A large number of plug-ins help to significantly expand the functionality.

What do you dislike?

At the beginning, the tool may seem a bit complicated, especially if you are a beginner. As for testing, it is not always possible to quickly interpret errors. Sometimes it is difficult to understand why the assembly broke. In addition, I would like to upgrade the interface.

Recommendations to others considering the product:

If you need the service ""all in one"" - then TeamCity - a godsend for you!

This service is easy to configure and starts for a very short time. Simplicity of scalability. TeamCity is well suited for small companies, but it can also be used for a large company with an enhanced package.

What problems are you solving with the product? What benefits have you realized?

My team had a need to create one common environment for all applications with the possibility of simple integration. So, TeamCity is an excellent tool for automatic assembly, testing and continuous deployment. This service has allowed us to improve the efficiency of the entire continuous delivery process.

Copy Review URL
Principal Architect and Development Manager
Financial Services
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Good for CI but has some snags"

What do you like best?

Easy to install and configure

Easy to use

What do you dislike?

Too frequent major updates, requiring IT time to re-setup. This is actually the biggest reason we are moving off of TeamCity.

Also, it was not designed with security in mind. For example, the register user page is turned on by default, which is a huge security hole because it allows anyone to create an account. And putting this web app behind an HTTPS-only connection doesn't quite work because the administration pages are hard-coded to link to HTTP (very poor coding practice), so then user has to manually change address to HTTPS again and again.

Recommendations to others considering the product:

Try it out and be sure to evaluate what it is going to be like when there is a new major version every year, and also do a security risk analysis.

What problems are you solving with the product? What benefits have you realized?

We configure both CI builds and for deploys, for multiple environments. Most of the time it works very well so that we don't even have to think about it.

Copy Review URL
Associate Software Engineer
Enterprise
(1001-5000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"TeamCity for builds"

What do you like best?

We can automate the process of kicking off the build. We can build multiple repositories and multiple branches at the same time. We get all the artifacts created that we can use later.

What do you dislike?

At times, the build doesn't kick off automatically. We have to start it.

What problems are you solving with the product? What benefits have you realized?

It becomes easy for QAs for testing and also for deployment team by just getting the build number. No need to worry about artifacts, etc.

Copy Review URL
Founder | Software Engineer | Educator
Small-Business
(Myself Only)
Validated Reviewer
Review Source
Copy Review URL

"Flexible!"

What do you like best?

It allows you to decide how to use it.

You can self host it and utilize AWS EC2 instances to run agents.

What do you dislike?

The interface can be a little cumbersome, but I don't have a suggestion on how to improve it...

Recommendations to others considering the product:

I would self host if you are a small company because there isn't a lot to get started. They do a good job of giving you all the tools you need to run it.

What problems are you solving with the product? What benefits have you realized?

We're able to build and deploy our software with ease as well as utilize a CI pipeline to rapidly release a SaaS.

Copy Review URL
Senior Developer
Marketing and Advertising
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"A Solid All Around Automation Tool"

What do you like best?

TeamCity integrates better with .NET tooling than any other automation system out there. From it we can build our pull requests from GitHub, run our unit tests, deploy to integration servers and run our smoke tests. It hooks in well with other JetBrains tools (we use Reharper and DotCover) and logs in with domain credentials, keeping life simple.

What do you dislike?

The configurations are not nearly as simple as they could be. When changing a setting, it is not always clear what is driven from the build master vs the build agent. It would also be much better if the program could update in place on its own, updates are a bit of a process.

What problems are you solving with the product? What benefits have you realized?

Before TeamCity, we did not have abny way of running our pull requests through a validation process. Now our code is all required to run and be tested on every commit. With the GitHub intergrations, we are even able to enforce that the tests are passing before the code moves forward. Our code is more stable and reliable thanks to TeamCity.

Copy Review URL
Leading Front-end Developer
Information Technology and Services
Enterprise
(1001-5000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Outstanding service! "

What do you like best?

TeamCity truly deserves to be called an "Intelligent CI server". No wonder why since it has so many amazing features such as detection of tool versions, testing frameworks support, code coverage, and static code analysis, etc. I thinks it is one of the best software out there that provides such a Continuous Integration server and Continuous Deployment platform at the same time.

What do you dislike?

I can't really find anything I do not like about it. It is just so good from the beginning to the end. It provides our company with everything we need and more.

Recommendations to others considering the product:

Get your hands on TeamCity as soon as possible! ;-)

What problems are you solving with the product? What benefits have you realized?

I cannot even fathom how else we would Integrate and deploy continuously our huge website without TeamCity. Our entire system depends on its high quality service.

Copy Review URL
Application Developer
Internet
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Most feature-complete CI server I've used"

What do you like best?

Once you've got TeamCity running you're just a few clicks away from the most pleasant setup experience around. You can easily extend the capabilities of your server by harnessing community developed plugins that are capable of just about anything, from running simple test suites to building games with the powerful Unity game engine.

What do you dislike?

Compared to the setup of services such as Atlassian Bamboo, Jenkins and Travis CI, TeamCity can be a drag to configure. Whilst it certainly is worth it in the long run it's simply a lengthy inconvenience for those who are tasked with doing it.

Recommendations to others considering the product:

Make sure to take full advantage of the free trial, you should be able to cram as much testing as you need in to ensure it's the right product for you. If you are looking to work with a specific language then you should check out the available plugins before trying it to make sure that said language is actually supported.

What problems are you solving with the product? What benefits have you realized?

TeamCity is primarily used to automate the periodic execution of various test suites we write for our projects, recently we've decided to take it a step further and have TeamCity deploy built artifacts to our bug finding environment before letting the QA testers have their way.

Copy Review URL
Concepteur/Développeur
Telecommunications
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"TeamCity is awesome you should use it if you're into continous integration"

What do you like best?

I previously worked for a software company that develop JEE applications. We had TeamCity for continuous integration and building. What we liked about it was the quality of the tool and even it's not a free one (although you can a limited environment for free package that includes the TeamCity CI server and three build agents) the paid support behind it. But even if it cost money, it's price is still affordable compared to Microsoft products (we had one .Net developer that used Visual Studio). We also liked one neat feature in TeamCity which is the web-based dashboard. It gave us a quick overview of our project status, additional to reporting information that can be convenient for a various kind of users and anyone involved in the project. It also gave us the build progress, ability to get more details with a drill down approach, in addition to historical data on the projects and configurations to keep an eye on changes.

What do you dislike?

May be the fact that it is not an open source project. We, especially in the java ecosystem, used to open source, we use other people work and give back to the community whenever it is possible.

Recommendations to others considering the product:

Give a try to TeamCity and you'll like how cool it is:

- TeamCity is extremely easy to setup, configure and use.

- TeamCity is deeply integrated with a lot of tools and technologies without need for complicated configurations,

- TeamCity is not that expensive compared to any commercial dev tools out there,

- TeamCity is secure,

What problems are you solving with the product? What benefits have you realized?

We used TeamCity for continuous integration of JEE applications, and to keep track on the how development is evolving and regression tests. We also made benefit of the code analysis built-in feature.

Copy Review URL
Owner
Information Technology and Services
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"The easiest-to-use and most feature-complete CI server you can find"

What do you like best?

Once TeamCity is up and running, configuration for projects and builds is a breeze. Community-provided plugins allows us to easily expand functionality (such as the Unity Runner for building Unity projects, or the SFTP Deployment plugin to handle deployments over SFTP). When compared to its alternatives, TeamCity's UI is both functional and aesthetically pleasing.

What do you dislike?

Initial installation/setup was not as smooth as some of the competition, which makes upgrading TeamCity a somewhat cumbersome process. As a result, we rarely upgrade unless a new release fixes a blocking or nuisance issue.

Built-in support for various languages is quite lacking. The bulk of our projects' build steps are shell scripts. Building projects using ant or MSBuild is incredibly easy, but for many other languages (for us, mainly Python) the initial setup of your build configuration can be a bit daunting.

Recommendations to others considering the product:

TeamCity's free license should be sufficient for an organization of any size to give the system a try and see if it will meet all business requirements.

What problems are you solving with the product? What benefits have you realized?

We use TeamCity to perform automated tests and, most recently, automated deployments to our staging environments. By removing the need for us to perform deployments manually, a bulk of our time has been freed up for other tasks.

Copy Review URL
Senior Software Engineer
Internet
Mid-Market
(501-1000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Great tool for managing builds and deploys"

What do you like best?

Totally flexible, but has good functionality out of the box. You can create your own processes and controls.

What do you dislike?

Can sometimes be confusing how to figure out what you can or can't do.

Recommendations to others considering the product:

This tool is not for amateurs, but the amount of up front time you invest it getting it working is well worth it. It is important to understand what you want out of your development processes, and have a clear set of guidelines and process controls before you start. But if you have these, TC will make it possible for you to manage things flexibly and in a distributed manner.

What problems are you solving with the product? What benefits have you realized?

We are using this for managing builds and deployments. It has allowed us to make significant progress towards our goal of Continuous integration, and has liberated our devops team from the necessity of always being involved in every release at every stage.

Copy Review URL
Lead Network Architect & SysOps
Information Technology and Services
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"An excelent and configurable CI server"

What do you like best?

TeamCity is a very flexible CI server. It can work with nearly any language or build system, provided the tools are present and can be run in a "headless" manner. Since the build process uses agents that can be installed remotely and on different operating systems, a single TeamCity server can be used for cross-platform development. Build steps are completely configurable and can range from built-in steps (MSBuild, Ant, etc) to scripts, to "meta-runners". It also supports displaying code coverage information, test output and VCS history.

What do you dislike?

The largest problem with TeamCity is that it's very memory-hungry. Expect to devote a server to the service if you're going to use it. It's coded in Java (like nearly all of JetBrains' other tools) on top of the Tomcat servlet engine. It's also just slightly custom enough that running it on a vanilla Tomcat install is very painful.

Recommendations to others considering the product:

There are a lot of CI solutions out there. TeamCity works best when you can self-host the system and have the in-house knowledge to maintain it. It may also be a great value as many services, such as Visual Studio Team Services can get expensive when you have complex and long-running build processes. TeamCity also has a no-cost license level, which is great for trial or usage by small companies.

What problems are you solving with the product? What benefits have you realized?

With a large, distributed team working on a complex project, it's very important to keep code quality in check. Automating tests and deploying to a QA testing environment helps keep turnaround fast and allows our developers to get quicker feedback on their code. TeamCity gives us confidence that our code will build and run properly.

Copy Review URL
Solutions Architect (APAC)
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"A must have for development team"

What do you like best?

TeamCity product is very stable and excellent in integration with TFS, it is very well engineered for developer in mind where each activity (build log) are extensively recorded and displayed with ease to navigate UI.

What do you dislike?

Some more refined TFS work item integration would be great, currently it only shows the 1st level of link to the TFS WI as issue list, but that doesn't go well with TFS Scrum template where WI is in hierarchical Feature/User Story/Task.

Recommendations to others considering the product:

To further pair with Octopus Deploy for deployment

What problems are you solving with the product? What benefits have you realized?

Uses TeamCity for automated Continuous Integration and Deployment for development team. It increases the quality of the deliverable where quality of code is being reported constantly.

Copy Review URL
Student Assistant
Higher Education
Enterprise
(1001-5000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"CI done Easily"

What do you like best?

TeamCity makes is very easy to implement DevOps in your organization on any scale.

What do you dislike?

While the initial setup can be a little difficult to understand and wrap your head around, it is very easy to setup and configure once you have understood some of the terms that TeamCity uses.

Recommendations to others considering the product:

If you use Git, or other VCS, consider TeamCity for your testing and deployment needs.

What problems are you solving with the product? What benefits have you realized?

TeamCity has made it possible for us to have a Testing/Staging/Production environment where all the stages are running the correct versions of our codebase. With excellent JUnit integration, as well as Build Status, we know quickly when one of our builds has failed and why.

Copy Review URL
Independent Software Developer
Computer Software
Small-Business
(Myself Only)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Versatile Continuous Integration solution with a LOT of features"

What do you like best?

The flexibility of the platform to fit complicated build scenarios, coupled with the amount of data it can give you, is what drives my love for this product. We have 100's of projects being built across many branches and build agents, and TeamCity makes it relatively easy to manage. It runs our tests, notifies when projects fail to build (before they hit our multi-hour overnight build process!) and it can package up products for use by internal teams.

What do you dislike?

It can be a very complex system, so when something goes wrong, we've had some difficulty tracking down exactly where the problem is. There are a LOT of settings, and each project could potentially have it's own unique set of configuration. Setting up the build agents from scratch is something that takes a while based on our software requirements, a way to spin these up in a more automated fashion would be nice if somehow incorporated into TeamCity.

Recommendations to others considering the product:

TeamCity really shines when you pair it with other products from Jetbrains. It isn't the easiest Continuous Integration system to set up, but by their very nature, few are. Taking the time to set up projects and dependencies from initial implementation, and using templates when possible, will save you a lot of time and headaches down the road.

What problems are you solving with the product? What benefits have you realized?

TeamCity is used to continuously build projects as developers make changes. It is responsible for running all of the unit tests on each check-in, and triggering any projects that may be downstream in the dependency chain, running tests on those projects as well. This has the primary benefit of being any early warning system to any changes that may impact functionality not only in the project changed, but in other products that make use of that project. This helps ensure our release build process will go smoothly each night, as problems are usually caught early by TeamCity while everyone is still in the office.

Copy Review URL
U
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Awesome, intuitive product for CI. Improved our process immensely!"

What do you like best?

I find it so much more intuitive and easier to use than some of the standard CI platforms out there. It is very reliable and has helped us improve our software development process immensely. It is easy to integrate custom scripts to generate builds or the standard plugins provided for things like Xcode and Android.

What do you dislike?

There is a little bit of a learning curve for the server side support. However, once learned, it is easy!

What problems are you solving with the product? What benefits have you realized?

Continuous Integration to improve software quality.

Copy Review URL
Mobile Developer
Internet
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"TeamCity has all the required features for an integration and build tool"

What do you like best?

TeamCity is a helpful and intuitive platform for continuous deployment of new builds and releases. It provides a clean user interface and has got easy navigation options.

It provides running automated tests in the build process and allows to view the issues along with detailed log information.

One of the best features of TeamCity is Publish Artifacts which allows anyone to deploy the code or even build directly in any environment such as development, testing, clone or production.

It shows the progress of the build at every step and the number of tests remaining to pass before the build is complete and turns green.

It also let you to rerun any of the failed test even after overnight execution of the same. This saves manually doing the execution again the next morning.

The overall functionality can be easily understood by going through the provided user guide which is thorough as well as extensive.

What do you dislike?

To setup the build configurations initially, it involves many steps because the process is broken down.

There is no option for deploying the application for the source code to be present in a particular build such as my main repository.

Recommendations to others considering the product:

If you are searching for an enterprise build management software, then TeamCity is definitely worth considering. It is also suitable for freelancer developers who have got a limited budget, as TeamCity is free up to certain number of projects.

What problems are you solving with the product? What benefits have you realized?

After using TeamCity, the process of continuous integration has become more concise and has also reduced the number of build failures. The issues gets highlighted pretty quickly and I am able to replicate issues on a fast track.

The best thing I found out was acceptance tests can be made to run after every single commit which provides faster response in the quality test.

A lot of time is saved with the automated deployments for scripts, applications and web services. This pipeline process has also reduced the manual errors.

Copy Review URL
GG
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Great continuous integration tool for help promote better software development practices."

What do you like best?

It is fairly easy to setup and start using right away, easy to setup permissions for different access levels.

Helps promote CI and has the ability to track history, notifications on events and monitor repositories for changes. Includes a windows system tray app to monitor in real time any events that you subscribe to.

Nice organization of projects and sub-projects with ability to create different builds for each project (Continuous Build vs Ad-hoc deployment builds)

What do you dislike?

Sometimes the Agents stop running for unknown reasons, event logs show nothing out of the ordinary so we need to restart the windows service for things to happen again. There is no notification so it might fail and we will be unaware of it until someone takes notice.

Recommendations to others considering the product:

Microsoft Team Foundation Server Build

What problems are you solving with the product? What benefits have you realized?

Help developers become away of issues when they check in code and are unaware that their changes have broken the build because they did not run tests locally. It also helps us schedule automated deployments to our integration environment weekly and ah-hoc deployments to our system test environments.

Copy Review URL
Software Engineer
Outsourcing/Offshoring
Mid-Market
(501-1000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Using TeamCity has been great so far!"

What do you like best?

We use Team City as our build server, and it has been great at letting us organize and track all of our builds. We have a 100+ solutions that are being contributed to and being built pretty frequently. We also use TC to kick off unit tests after each build and let us know if there are any failures via email.

What do you dislike?

Setting up a build could be simpler. We use a pretty basic setup - but I feel like I have to jump through hoops to get everything correct. I understand that having options complete multiple steps is important, but maybe these extra steps could be added in at will, not included in ever basic setup.

What problems are you solving with the product? What benefits have you realized?

I have worked at a few places, and each seemed to have a different solution for a build server. Team City has been the one I have been the most involved with, and also the easiest to use so far.

Copy Review URL
Software Engineer
Information Technology and Services
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"CI Solution from JetBrains. Easy to configure and manage. used it extensively for our java projects"

What do you like best?

i was first introduced to teamcity when contributing upstream to mesosphere projects. there i saw that their gating runs very fast and steady and on an environment called teamcity.

i was impressed and tried my own on my windows machine.

needless to say, the interface , the visibility and ergonomics were brilliant. for instance:

Cross-platform builds

The fact that it's based on Java does not hinder it's capability to support different build environments. TeamCity supports a large number of tools and languages.

Easy installation

TeamCity's installation is really simple. It has different installation packages for different operating systems. All that's needed is to download the correct one and run it.

What do you dislike?

Projects and configurations are not kept under VCS

TeamCity does not keep projects and configurations under Version Control. This means that deploying older revisions of a project is almost impossible is TeamCity has complete control over the source code and deployment packages.

Besides, you probably cannot use this approach with free version of TeamCity, because it does not allow having more than 20 configurations per project.

Recommendations to others considering the product:

please try first, and integrate before releasing out to average users.

What problems are you solving with the product? What benefits have you realized?

TeamCity provides nice set of feature for building your project and packing result binaries into deployment package. You can use them to get a quick start (of course if you already have some experience with these features). But keep in mind that TeamCity is not a Holy Grail of continuous integration process. Having 100% dependency on TeamCity is not good. There might be a moment when you have to build and package your project without TeamCity. So try to create stand-alone build scripts and use TeamCity only for calling these scripts when certain events occur (new commit, time schedule, user request, etc.).

What TeamCity does really well is running automated tests and reporting their status.

Copy Review URL
GC
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"We use this for our CI builds"

What do you like best?

It provides a good way to setup builds, and run unit tests with github checkins. We have it setup to run unit tests for our mobile apps whenever someone submits a pull request to github.

What do you dislike?

The github integration setup could be easier. It might be nice to just have pre-set check boxes to determine when you want something to be run, instead of using some branch syntax to determine that.

What problems are you solving with the product? What benefits have you realized?

This helps us build quality products since we are able to run unit tests each time a new commit is made. This helps us know up front if something in the commit is wrong rather than in production.

Copy Review URL
GC
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"TeamCity makes automated build easy."

What do you like best?

TeamCity is such an improvement on the old XML-based build systems of the past. It has a user interface that makes the entire build process easier and integrates with all the relevant systems and source control providers and even allows you to use Amazon AWS to utilise the cloud for build agents.

What do you dislike?

It can be somewhat daunting to a beginner but that is really more down to the power that it has and is based on the complexity of building software and all the various dependancies a software build has. There are worse interfaces out there and the help documentaion helps you manage this.

Recommendations to others considering the product:

TeamCity is probably the easiest build server setup i have used and it has all the pieces needed to get the job done and is priced fairly and even has a freemium style pricing so you can kick the tyres on it.

What problems are you solving with the product? What benefits have you realized?

Build automation via collecting your latest code from source control and all the depandanices needed to procuce the artifacts ready to actually deploy software to various environments.

Copy Review URL
ET
Mid-Market
(201-500 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Decent CI/CD Software"

What do you like best?

It was very easy to setup. The interface is logically laid out. It supports a number of nice features including automated tests, dependency checks, support for many different code repositories including cvs and svn, and requires only occasional maintenance.

What do you dislike?

It doesn't integrate with our other Atlasssian products as nicely as Bamboo does. Which to be fair is expected as Bamboo is also an Atlasssian product. Builds will typically generate a fair amount of files and artifacts which can quickly consume disk space. The cleanup routines within Teamcity need to be carefully tuned to avoid filling your disks. This can become an onerous task.

Recommendations to others considering the product:

TeamCity is roughly equivalent to Jenkins and Bamboo. With Jenkins it's very extensible but will require more manual configuration and fiddling versus TeamCity and Bamboo which are both polished commercial products. If you are already using Atlasssian products, you'll gain better integration by using Bamboo. If you aren't an Atlasssian shop, then TeamCity offers similar functionality. You'll need to make your decision based on current features, UI, and prices for each.

What problems are you solving with the product? What benefits have you realized?

We were looking for a good continuous integration, testing, and deployment server

Copy Review URL
Senior MicroStrategy Developer
Internet
Mid-Market
(201-500 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Paid continuous integration"

What do you like best?

Many options, Java based so easy to integrate a Maven project.

Coming from Jenkins I found TeamCity annoyingly complicated, even setting it up using docker was not easy.

What do you dislike?

Bad documentation, difficult to find help Googling problems, cumbersome setup. I wanted my Jenkins back as soon as possible

Recommendations to others considering the product:

Check Jenkins before using TeamCity, if Jenkins is enough (probably it will be even more) for your requirements go with it and forget about TeamCity.

What problems are you solving with the product? What benefits have you realized?

Build and deployment of a web application on different Tomcat server (for development, testing and production) using different Maven profiles.

Copy Review URL
Head of Internal Platform Development Unit
Banking
Enterprise
(5001-10,000 employees)
Validated Reviewer
Review Source
Copy Review URL

"Easy to setup and use build server"

What do you like best?

The best thing is that the UI is very user friendly and easy to set up. The functionality is also very flexible and powerful. Also it supports all of the popular version control systems so it can work with any of them. Also the free Pro version comes with enough build configurations to use the system for many different projects.

What do you dislike?

Teamcity has many configuration options and powerful functionality so it can be overwhelming to navigate and understand all the available options.

Recommendations to others considering the product:

I would recommend to start using TeamCity as soon as possible and automate your builds and deployments.

What problems are you solving with the product? What benefits have you realized?

Teamcity allows us to quickly identify all the failed builds and deploy code to test and live environment without manual work.

TeamCity Pricing

TeamCity User Ratings

7.9
Ease of Use
Average: 8.4*
8.1
Quality of Support
Average: 8.1*
7.3
Ease of Setup
Average: 8.1*
* Continuous Integration Category
Do you work for TeamCity?