JFrog Pipeline vs Jenkins comparison

Jenkins and JFrog are both solutions in the Build Automation category. Jenkins is ranked #3 with an average rating of 8.1, while JFrog is ranked #23. Jenkins holds a 10.5% mindshare in BA, compared to JFrog’s 1.3% mindshare. Additionally, 87% of Jenkins users are willing to recommend the solution, compared to 100% of JFrog users who would recommend it.

Jenkins

Read 93 Jenkins reviews

3,625 Views
2,329 Comparison Views

87% willing to recommend

JFrog Pipeline

Read 1 JFrog Pipeline review

407 Views
289 Comparison Views

100% willing to recommend

Jenkins

JFrog Pipeline

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between Jenkins and JFrog Pipeline 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: June 2025).

Buyer's Guide

Build Automation

June 2025

Download the complete report

Helped 860,592 peers since 2012

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

Jenkins

Ranking in Build Automation

3rd

Average Rating

8.0

Reviews Sentiment

7.0

Number of Reviews

Ranking in other categories

No ranking in other categories

JFrog Pipeline

Ranking in Build Automation

23rd

Average Rating

8.0

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of July 2025, in the Build Automation category, the mindshare of Jenkins is 10.5%, down from 12.7% compared to the previous year. The mindshare of JFrog Pipeline is 1.3%, up from 1.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Mahdi Mallaki

Senior Devops Engineer at Rakuten

Has a community of plugin providers but needs improvement in Kubernetes integration

Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests. In contrast, GitLab offers an integrated Git repository and pipeline runner, streamlining the process. One improvement for Jenkins could be integrating a Git server, simplifying the management of CI/CD pipelines. Currently, with Jenkins, modifying pipeline manifests requires navigating to a separate Git repository. In GitLab, however, manifest changes can be made directly within the repository.

Read full review

Steve Buttler

DevOps Lead at a tech company with 51-200 employees

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

Quotes from Members

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

Pros

"Has a good interface, is reliable and saves time."

"Has enabled full automation of the company."

"The most valuable feature of the solution is its integration between different tools."

"The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."

"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."

"Jenkins's open-based framework is very valuable."

"Jenkins is very customizable."

"I like the business logs. It's a very useful tool. Client-server communication is also very fast."

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

Cons

"I would like to see even more integrations included in the next release."

"Jenkins can sometimes run slow, especially when restarting after a plugin installation or when returning from a pipeline view to the dashboard."

"Logging could be improved to offer a clearer view."

"Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests."

"Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."

"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."

"The UI of Jenkins could improve."

"It can be improved by including automated mobile reporting integrations."

More Jenkins cons

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

Pricing and Cost Advice

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"It is an open source."

"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."

"The solution is one of the lowest costs compared to competitors."

"It could be cheaper because there are many solutions available in the market. We are paying yearly."

"We are using the free version of Jenkins. There are no costs or licensing."

"Jenkins is an open-source platform."

More Jenkins pricing and cost advice

"The pricing is the cheapest compared to the other platforms out there."

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

860,592 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

Financial Services Firm

21%

Computer Software Company

16%

Manufacturing Company

12%

Government

Financial Services Firm

21%

Computer Software Company

11%

Manufacturing Company

Comms Service Provider

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

Questions from the Community

How does Tekton compare with Jenkins?

When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...

See all answers

What do you like most about Jenkins?

Jenkins has been instrumental in automating our build and deployment processes.

See all answers

What is your experience regarding pricing and costs for Jenkins?

Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.

See all answers

Ask a question

Earn 20 points

Comparisons

Harness vs Jenkins

Compared 17% of the time

GitLab vs Jenkins

Compared 14% of the time

Bazel vs Jenkins

Compared 9% of the time

Tekton vs Jenkins

Compared 8% of the time

TeamCity vs Jenkins

Compared 7% of the time

More Jenkins Competitors

GitHub Actions vs JFrog Pipeline

Compared 18% of the time

Buildkite vs JFrog Pipeline

Compared 13% of the time

More JFrog Pipeline Competitors

Product Reports

Buyer's Guide

Jenkins

June 2025

Download Jenkins product report

Buyer's Guide

Build Automation

June 2025

Download JFrog Pipeline product report

Also Known As

No data available

Shippable

Overview

Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

Jenkins

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.

JFrog

Sample Customers

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox

SAP, Today Tix, Cisco, Lithium, Pushspring, Packet

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

DOWNLOAD NOW

860,592 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.