TeamCity Reviews

We generally use TeamCity for automation and development.

TeamCity's GUI is nice.

One thing comes to mind, but maybe it's more of an issue on our side and not a problem with TeamCity itself. We don't have the high availability package. So I'd like our company to purchase that. So when one goes down, then we have a backup. I think we've purchased it, but we just haven't had anyone with the time to implement it. I think there was an extra cost, but we did buy it, and then I think you have to set it up in a certain way.

I've been using TeamCity for about three years. 

It's easy to scale, but this is on RDS, so you can scale it up and down. I don't think we purchased the scaling features, but they do have scalability. All of our developers are using it, so more than a hundred.

We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US. Still, the tech support is pretty good. Even the original person that wrote the product is still working there, so that's good. But we have issues with the time zone.

It can be pretty complex. There's the RDS setup, where you use RDS, and you have agents and whatnot. I wouldn't say it's super complex. At the same time, it's not something where you just click a button, and you're done. It's kind of in the middle range. 

TeamCity is on the expensive side. It's more for developers than CIS admins. Conversely, Ansible is more for CIS admins and less for developers. It would be nice to have a solution that works for both purposes. So I think Ansible was something they were thinking about purchasing, but I'm not sure if that ever occurred.

There are two teams — on-prem and cloud — and the cloud team uses TeamCity. On-prem uses SUSE automation.

I rate TeamCity eight out of 10.

I spend less time scripting to get a build working and more time configuring TeamCity through its web-based front end.

It delegates the building of executable code to a machine.

More build runners and more options are needed, although I have no worries they keep improving.

This is the second job I have used it at. I have used other CI systems in the past, but I have been using TeamCity around two years.

Actually, I ran into a problem and I needed to do a fresh install. TeamCity stores its configuration data separate from where it installs. so this makes upgrades smoother, but makes it harder to start with a fresh slate. The problem was the data directory of the service account was rerouted because it was a 64 bit OS to SysWOW64.

No, it stays running and performs build regularly.

For our usage, it has scaled well to our needs.

10/10 - their service is very professional and prompt.

10/10 - their service is very professional and prompt, and their staff really wants to solve your problems.

I had used CruiseControl.NET in the past. It was useful once running, but painful to initially setup, and we used word of mouth and articles showing comparisons with other frameworks.

Just installing it with one agent is a breeze. The starting free license comes with three build agents, which, if you install them all as services, takes a little modifying of config files and running of batch files.

I implemented it.

Yet to be calculated. I am trying to automate the release of deliverables to free someone's time up.

Start with the free license it has decent room for one group.

Start small. Start with just doing builds before executing tests.

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