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

JFrog Pipeline vs TeamCity comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

JFrog Pipeline
Ranking in Build Automation
25th
Average Rating
8.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
TeamCity
Ranking in Build Automation
9th
Average Rating
8.2
Number of Reviews
28
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2025, in the Build Automation category, the mindshare of JFrog Pipeline is 1.1%, up from 0.9% compared to the previous year. The mindshare of TeamCity is 7.3%, up from 6.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Steve Buttler - PeerSpot reviewer
Testing against multiple run times, versions, and environments is a plus point
We are using Shippable to automate our CI/CD, so we (and our developers) can focus on our core business.  Shippable has tremendously increased our product and features delivery by at least three times. The platform has some amazing features and the integration option makes it very simple to plug…
Omakoji Idakwoji - PeerSpot reviewer
Build management system used to successfully create full request tests and run security scans
I find the TeamCity backend easily accessible. Users can login to the Linux servers that TeamCity is installed on and perform operations. Also I find the ability to template solutions using the meta runner a good feature as well as the user management feature. There is a display that shows which user made recent changes to a branch on GitHub, including the time the changes were made and the particular agent that ran the job. This is also a very useful feature. The metrics and audit available for projects, pipelines and jobs come in handy when debugging.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."
"Testing against multiple run times, versions, and environments is a plus point with the additional pipelines making it more interesting to see what is happening across your development process in a single pane of glass."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"Good integration with IDE and JetBrains products."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"TeamCity is more structured and user-friendly than other vendors."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"VCS Trigger: Provides excellent source control support."
 

Cons

"They could work on reducing the number of permissions required while using Bitbucket."
"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."
"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."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"The integration between other solutions and TeamCity could be smoother."
"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."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
 

Pricing and Cost Advice

"The pricing is the cheapest compared to the other platforms out there."
"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."
"The licensing is on an annual basis."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
838,713 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
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…
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
13%
Manufacturing Company
8%
Educational Organization
8%
Financial Services Firm
26%
Computer Software Company
17%
Manufacturing Company
6%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about TeamCity?
One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.
What is your experience regarding pricing and costs for TeamCity?
Compared to new technologies, TeamCity is more expensive and is an older tool compared to tools like GitLab.
What needs improvement with TeamCity?
TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related ...
 

Comparisons

 

Also Known As

Shippable
No data available
 

Overview

 

Sample Customers

SAP, Today Tix, Cisco, Lithium, Pushspring, Packet
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation. Updated: January 2025.
838,713 professionals have used our research since 2012.