We performed a comparison between Jenkins and TeamCity based on real PeerSpot user reviews.
Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins."
"Has enabled full automation of the company."
"It's very easy to learn."
"A lot of support material exists via a single web search of exactly what you're looking for."
"The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."
"There are a large number of plugins available for integration with third party systems."
"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."
"It is easy to use."
"TeamCity's GUI is nice."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"The integration is a valuable feature."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end."
"The learning curve is quite steep at the moment."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS."
"We cannot change the ownership of any directory or file or any kind of directory."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"The support for the latest Java Runtime Environment should be improved."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I need some more graphical design."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone) to provide training classes to help newcomers get things up and running more quickly."
"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."
"The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs."
Jenkins is ranked 2nd in Build Automation with 83 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. Jenkins is rated 8.0, while TeamCity is rated 8.2. The top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Digital.ai Release , whereas TeamCity is most compared with GitLab, CircleCI, Harness, Tekton and GitHub Actions. See our Jenkins vs. TeamCity report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.