No more typing reviews! Try our Samantha, our new voice AI agent.

JFrog Pipeline vs Tekton 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
23rd
Average Rating
8.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
4th
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
37
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2026, in the Build Automation category, the mindshare of JFrog Pipeline is 2.1%, up from 1.4% compared to the previous year. The mindshare of Tekton is 4.7%, down from 11.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Tekton4.7%
JFrog Pipeline2.1%
Other93.2%
Build Automation
 

Featured Reviews

Steve Buttler - PeerSpot reviewer
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…
reviewer2741265 - PeerSpot reviewer
Software engineer at a manufacturing company with 10,001+ employees
Benefit from a smooth learning curve and efficient adaptability
After seeing Jenkins and Tekton, I think Tekton is quite built on top of Kubernetes, so the learning curve is minimal. If you are working with Kubernetes, then OpenShift created Tekton on top of that, making it easily adaptable. Tekton is highly customizable. With Kubernetes, we can customize on our own and create custom builders. If teams have time and want to make enhancements, they can do it themselves. Whatever OpenShift is providing regarding Tekton is sufficient. It is easy to use because we don't need to write every pod step every time. A proper DevOps engineer can help once or twice, and development teams can easily adapt to that, make small shell script changes in the steps, understand the process, and work with it.

Quotes from Members

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

Pros

"Shippable has tremendously increased our product and features delivery by at least three times."
"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."
"Tekton is highly customizable, with Kubernetes, we can customize on our own and create custom builders."
"The flexibility of Tekton is the most valuable feature"
"Tekton's inclusion in Kubernetes deployment offers better visibility on how Tekton is performing within a cluster. It is lightweight and not as heavy as Jenkins to maintain."
"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."
"Tekton is a stable product."
"When you run a pipeline, all the jobs are called. It is a very valuable feature that enhances job maintenance overall."
"The product's best feature is its ease of implementation."
"We can make a lot of customizations, and data sharing between tasks using workspaces is very convenient."
 

Cons

"They could work on reducing the number of permissions required while using Bitbucket."
"Tekton could improve by adding better documentation."
"Some of the tool's cons include its minimalistic dashboard, which lacks detailed information and control compared to other tools like Jenkins or GitLab. Additionally, it's primarily used by Japanese companies."
"The user interface of Tekton could be improved."
"The stability issues can be there."
"When we started with Tekton around 2021 or early 2022, the community support was somewhat limited, which posed challenges when dealing with issues or debugging. We had to rely on Red Hat OpenShift support to overcome these challenges. However, I believe that these issues will naturally improve over timeas the developer community grows stronger. From a technical perspective, I haven't had the opportunity to deeply evaluate the product end-to-end, especially in the past year or so, when I've been less involved with it."
"Tekton lacks integration capabilities compared to other CI/CD tools like Jenkins and Travis."
"One area where Tekton can improve is log management."
"Compared to traditional tools like Jenkins, Tekton lacks a lot of features. It's not efficient in managing conflicts between multiple pipelines."
 

Pricing and Cost Advice

"The pricing is the cheapest compared to the other platforms out there."
"The product is free and open-source."
"The product is free of cost."
"The solution is open-source."
"It is entirely open source and free of charge."
"Tekton is an open-source tool."
"The tool is open-source and free to use."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
904,973 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Manufacturing Company
9%
Comms Service Provider
6%
Construction Company
6%
Financial Services Firm
21%
Manufacturing Company
10%
Computer Software Company
6%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise23
 

Questions from the Community

Ask a question
Earn 20 points
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...
What needs improvement with Tekton?
I didn't get the intention of scalability. Scalability means based on the load, it will automatically gain resources and run. The question of pipeline scalability remains unclear. It's quite easy t...
What is your primary use case for Tekton?
We use Tekton for build and deployments. For LMP testing, we use the Tekton pipeline. We also use GitHub CI/CD. For infrastructure pipelines and Infrastructure as Code (IaC), we use Tekton. Previou...
 

Comparisons

 

Also Known As

Shippable
No data available
 

Overview

 

Sample Customers

SAP, Today Tix, Cisco, Lithium, Pushspring, Packet
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about GitLab, Jenkins, GitHub and others in Build Automation. Updated: July 2026.
904,973 professionals have used our research since 2012.