JFrog Pipeline vs TeamCity comparison

JFrog and JetBrains are both solutions in the Build Automation category. JFrog is ranked #26, while JetBrains is ranked #10 with an average rating of 6.0. JFrog holds a 1.0% mindshare in BA, compared to JetBrains’s 6.8% mindshare. Additionally, 100% of JFrog users are willing to recommend the solution, compared to 89% of JetBrains users who would recommend it.

JFrog Pipeline

Read 1 JFrog Pipeline review

339 Views
302 Comparison Views

100% willing to recommend

TeamCity

Read 27 TeamCity reviews

2,643 Views
2,335 Comparison Views

89% willing to recommend

JFrog Pipeline

TeamCity

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between JFrog Pipeline and TeamCity based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation.

To learn more, read our detailed Build Automation Report (Updated: October 2024).

Buyer's Guide

Build Automation

October 2024

Download the complete report

Helped 814,649 peers since 2012

Categories and Ranking

JFrog Pipeline

Ranking in Build Automation

26th

Average Rating

8.0

Number of Reviews

Ranking in other categories

No ranking in other categories

TeamCity

Ranking in Build Automation

10th

Average Rating

8.0

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of November 2024, in the Build Automation category, the mindshare of JFrog Pipeline is 1.0%, up from 0.8% compared to the previous year. The mindshare of TeamCity is 6.8%, down from 7.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Steve Buttler

DevOps Lead at a tech company with 51-200 employees

Jan 19, 2018

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…

Read full review

Omakoji Idakwoji

Software Engineer at Home Depot

Jul 25, 2022

Build management system used to successfully create full request tests and run security scans

We use it for running unit tests for merge requests on github. We also use it to build executable artifacts and also for running security scans Time to deployment has been reduced. It has helped in preventing us from deploying breaking changes into production. If the pipelines are configured…

Read full review

Quotes from Members

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

Pros

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

"The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."

"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."

"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."

"TeamCity's GUI is nice."

"TeamCity is very useful due to the fact that it has a strong plug-in system."

"Good integration with IDE and JetBrains products."

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

"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."

More TeamCity pros

Cons

"They could work on reducing the number of permissions required while using Bitbucket."

"REST API support lacks many features in customization of builds, jobs, and settings."

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

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

"The integration between other solutions and TeamCity could be smoother."

"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."

"I need some more graphical design."

More TeamCity cons

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

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

814,649 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

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…

Read full review

Top Industries

By visitors reading reviews

No data available

Financial Services Firm

27%

Computer Software Company

16%

Manufacturing Company

Retailer

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.

See all answers

What needs improvement with TeamCity?

The integration between Bitbucket and TeamCity could be smoother. I encountered challenges when passing data from Visual Studio to Bitbucket and TeamCity. Improved documentation or out-of-the-box c...

See all answers

What is your primary use case for TeamCity?

I used the product to deploy changes to UAT for testing and then to production.

See all answers

Comparisons

Jenkins vs JFrog Pipeline

Compared 80% of the time

Harness vs JFrog Pipeline

Compared 20% of the time

More JFrog Pipeline Competitors

GitLab vs TeamCity

Compared 39% of the time

GitHub Actions vs TeamCity

Compared 16% of the time

CircleCI vs TeamCity

Compared 13% of the time

Harness vs TeamCity

Compared 10% of the time

Tekton vs TeamCity

Compared 8% of the time

More TeamCity Competitors

Product Reports

Buyer's Guide

Build Automation

October 2024

Download JFrog Pipeline product report

Buyer's Guide

TeamCity

October 2024

Download TeamCity product report

Also Known As

Shippable

No data available

Learn More

JFrog

JetBrains

Overview

JFrog Pipelines empowers software teams to ship updates faster by automating DevOps processes in a continuously streamlined and secure way across all their teams and tools. Encompassing continuous integration (CI), continuous delivery (CD), infrastructure and more, it automates everything from code to production. Pipelines is natively integrated with the JFrog Platform and is available with both cloud (software-as-a-service) and on-prem subscriptions.

TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

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: October 2024.

DOWNLOAD NOW

814,649 professionals have used our research since 2012.

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.