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

JFrog Pipeline vs Tekton comparison

Why PeerSpot?
 

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
24th
Average Rating
8.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
7th
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 October 2026, in the Build Automation category, the mindshare of JFrog Pipeline is 1.9%, up from 1.8% compared to the previous year. The mindshare of Tekton is 4.0%, down from 9.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Tekton4.0%
JFrog Pipeline1.9%
Other94.1%
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."
"It scales automatically based on the number of tasks or pipelines running, which is efficient and effective for our development needs."
"Tekton's most important feature is its cloud-native nature. Unlike Jenkins, which may not scale as efficiently, Tekton's CI pipeline can automatically scale up to handle increased workload demands without needing manual adjustments."
"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 cloud-native solution. It offers optimal resource consumption, allowing tasks to be run more efficiently and at a lower cost."
"I would say the customization ability that Tekton provides is good."
"I like the branching and visualization tools for the pipeline."
"You can isolate most Tekton assets in the Kubernetes namespace for your feature branch. This allows you to freely change Tekton assets and objects to adapt to your feature branch and requirements."
"I like the setup of the dashboard."
 

Cons

"They could work on reducing the number of permissions required while using Bitbucket."
"Tekton could improve by adding better documentation."
"The question of pipeline scalability remains unclear."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
"RBAC is really needed for Tekton."
"One area where Tekton can improve is log management."
"Improvements could include introducing a UI-based pipeline development feature, such as drag and drop, which would help individuals with limited technical knowledge start building pipelines."
"Tekton lacks integration capabilities compared to other CI/CD tools like Jenkins and Travis."
"The product's scalability can be challenging when multiple users access it simultaneously."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Insurance Company
11%
Comms Service Provider
11%
Manufacturing Company
7%
Financial Services Firm
20%
Manufacturing Company
11%
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 Jenkins, GitHub, GitLab and others in Build Automation. Updated: October 2026.
917,433 professionals have used our research since 2012.