TeamCity Reviews

• It's a very useful, intuitive tool to continuously deploy new builds
• A clean user interface
• It's very easy to use, even for non-build engineers
• Ability to run automated tests as part of the build process
• Easy to pinpoint issues with the detailed logs
• Easy navigation
• Useful to see how the build is progressing and how many tests are left to pass before the build is green

• Improved the quality of builds by running unit tests as part of every build
• Reduced the risks of regression defects by running automated tests as part of the build process

The UI could be more structured, as it is so customisable it is quite easy to get lost around the screens.

I have used this product for over six months now.

Only environment issues which caused failed deployments. Also, if people were connected to the database on the backend, the build would fail.

It seemed a very stable tool with hardly any downtime in the six months I was using it.

Not at all. In fact it was so stable we were able to add and create our own virtual environments each time we needed to deploy. This meant that each user had their own virtual environment, meaning nothing ever got overwritten.

I had no need for it as we had DevOps engineers who fixed any issues.

I used to use Jenkins in a previous job. I started using TeamCity when I changed jobs as that was the tool that was being used, but I preferred TeamCity to Jenkins.

It's fairly straightforward.

It was implemented by an in-house team.

We used to deploy multiple times a day too many different environments. Also, we had offices in Australia who were using it when we were asleep! Effectively we were using this tool 24 hours a day, seven days a week.

Do it! Very easy to use and very stable. A must have tool for any teams using agile methodologies.

The ability to create Build Pipelines and create user groups are the two most valuable features.

• As a business we had a custom build process where the only people with access to the build were our build engineers.
• Teamcity allowed us to create a visual flow of the processes and steps involved in moving a build through its phases.
• The product also allowed us to identify areas for improvement in our process.

This product lacks real reporting for all the information it captures; we should be able to create reports or dashboards for management.

The product captures a lot of information about build processes, but there is no easy way to create/generate reports that can be used by management.

We have been using TeamCity for about 6 – 7 years.

There were no issues with deployment.

There were no issues with stability.

It would be ideal if agents could scale up on demand using a private cloud. The functionality is there for Amazon.

Good.

Excellent.

The setup is extremely straightforward.

In-house implementation.

We evaluated a few other products. The only product that had was a real contender was Electric Commander.

We are using the latest version of TeamCity by JetBrains, 2021. 

We needed CI/CD, a Continuous Integration Delivery approach to our current process and the database development process. We needed a tool to generate and run automated builds and tests and to notify us in the event of a failure.

The integration is a valuable feature. The solution comes with a great CI/CD flow. As we have our own personal server, we have our own account for each developer. When it comes to access to it's dashboard it can be integrated with a social control. We integrated with version control and did so with GitHub. It allows one to have repositories in a single place, so as to customize the whole desired flow for having an initial continuous integration of a working build.

We would like to see better integration with other version controls, since we encountered difficulty when this was first attempted. This meant that we had to use predefined scripts that we wrote on our own.

When it comes to other source control tools , such as GitHub, it's really straightforward and easy to do.

We've been using TeamCity over the past 12 months. 

The initial setup was straightforward. I can log in and start working as soon as I have my account credentials. While some advance training is needed, the person would be good to go once he has mastered the basics. 

When it comes to plans to increase usage, this depends on the company and the user developer.

I have not had occasion to make use of the solution's technical support. 

The licensing is on an annual basis.

I cannot comment on the pricing, as this is out of my purview. 

We did not evaluate other options prior to going with TeamCity. It was the first one we picked for the integration of our CI/CD.

We have more than 50 users in our organization who are making use of the solution.

There is much online documentation for TeamCity, with certain learning materials such as videos. There are many free courses, as well.

Someone considering the implementation of TeamCity should first define all of his use cases. If the person wishes to integrate it with infrastructure, but is a junior engineer who lacks experience with DevOps tools, he would need to do some learning. This said, the solution is a great tool for CI/CD. 

The solution has all the features that I need, with a good user interface. I'm pretty satisfied.

I rate TeamCity as an eight out of ten. 

• Centralized build automation
• Ability to embed powershell scripts for automated deployments
• Auditability of builds
• Unit tests
• Smoke tests
• Automated deployments

Continuous integration has reduced build failures and highlighted issues sooner. Automated deployments of web services, database scripts and applications chained across all environments has minimized time and effort, sped up delivery time, reduced risk of human error and enabled automated communication to stakeholders via integration with JIRA for release notes.

I've used it for three years.

Occasionally issues deploying software using the tool due to configuration issues within the tool (mostly around powershell configuration).

We had to add additional servers to enable a failover capability, but this was more to do with our infrastructure

No issues enquired.

I've not required customer service.

It's good. It's done via online forums.

We previously used Jenkins and Cruise control. We changed to enable one common solution and standard support model, also better functionality.

It was very simple. I have also installed on my home server to enable me to continue to develop and learn the tool.

We did it in-house.

The initial cost was only the cost of a virtual server, and database which was less than 1000 Euros a month. I am not aware of ongoing costs.

No other options were evaluated.

Make sure you define the standards and naming conventions prior to implementing TeamCity.

• General ease of use
• Quick start up time
• NUnit build runner

• Continuous deployment
• Continuous integration
• Testing feedback

I've used it for four years.

No issues encountered.

No issues encountered.

No issues encountered.

There was no previous solution in place.

It's straightforward as the UI is intuitive.

I implemented it myself.

It's free, so very good.

Start with the free version, and go from there.

No other options were evaluated.

Get someone who knows it well to go through the basics, but there's also loads of help on Google.

VCS Trigger: Provides excellent source control support. Able to customize a feature with the specific conditions we want. For example, if we wanted only a specific branch to trigger a build, we can do that. 

Automatic VCS Triggers, MSTest, and NUnit integration made our workflow much faster and efficient. It just felt more mature and everything was working as we expected.

The upgrade process could be smoother. Upgrading major versions can often cause some pain.

We did not encounter any serious issues with stability so far.

No issues with scalability. When we needed more agents, we simply used pre-configured machines and quickly installed the agent on them.

Great tech support with quick response times.

TFS, back at the time TFS carried too much overhead for us. So, we looked for a better solution out there. When we discovered TeamCity, it totally speeded up our workflow. TeamCity's configuration and ease of use are way better compared to TFS, which eventually saved us a lot of time. 

One of the things I liked about TeamCity. It is very easy to install and maintain.

Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most.

Jenkins, but it was not mature enough and did not meet our needs at that time.

It really is dependent on your product needs. Do market research and see the pros and cons versus open source or any other solutions out there.

• Continuous integration
• Build templates
• Triggers
• Plugins
• Platform independence

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.

Deployment functions need work.

I've used it for two years.

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

No issues encountered.

No issues encountered.

Good. I would give them a 9/10.

Good. I would give them a 9/10.

No previous solution was used.

Simple and easy to integrate with Subversion source code tool.

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

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