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

Jenkins vs Tekton comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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
4th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
92
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
2nd
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 February 2026, in the Build Automation category, the mindshare of Jenkins is 7.2%, down from 11.1% compared to the previous year. The mindshare of Tekton is 7.0%, down from 12.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Tekton7.0%
Jenkins7.2%
Other85.8%
Build Automation
 

Featured Reviews

JI
Principal Software Engineer at a financial services firm with 5,001-10,000 employees
Efficient resource allocation and robust workflow with autoscaling capabilities
In Kubernetes, we use node-based architecture with nodes and pods and follow practices like RBAC and rollback. Multiple pods can run concurrently. We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load.
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

"It is very useful for us to be able to collect and manage automatic processing pipelines."
"The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."
"The deployment of traditional Jenkins is easy."
"The most valuable feature is its ability to connect with different tools and technologies."
"The initial setup is pretty simple."
"Has enabled full automation of the company."
"The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins."
"It is easy to use."
"The product's best feature is its ease of implementation."
"Tekton is serverless and runs on OpenShift, and we leverage Tekton to take full advantage of the Kubernetes features such as running and scaling the solution in PaaS."
"Tekton provides a feature where you can schedule the job."
"Tekton is a stable product."
"I would say the customization ability that Tekton provides is good."
"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."
"The tool's most valuable aspect is its compatibility with the cloud-native environment. It can be easily installed on Kubernetes and leverages its resources to run CI/CD pipelines."
"I find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."
 

Cons

"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"We cannot change the ownership of any directory or file or any kind of directory."
"A more user-friendly UI for creating pipelines would be helpful."
"Jenkins needs a faster deployment process."
"The upgrades need improvement."
"The support for the latest Java Runtime Environment should be improved."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
"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 could improve by adding better documentation."
"The user interface of Tekton could be improved."
"Improvement is needed in the documentation and the overall integration process."
"There might be occasional issues with storage or cluster-level logging, which can affect production."
"RBAC is really needed for Tekton."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
 

Pricing and Cost Advice

"Jenkins is an open-source platform."
"The tool is open-source."
"Jenkins is open source and free."
"The solution is open source."
"Jenkins is not expensive and reasonably priced."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"The pricing for Jenkins is free."
"We are using the freeware version of Jenkins."
"Tekton is an open-source tool."
"It is entirely open source and free of charge."
"The tool is open-source and free to use."
"The product is free of cost."
"The product is free and open-source."
"The solution is open-source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
881,733 professionals have used our research since 2012.
 

Comparison Review

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

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Manufacturing Company
14%
Computer Software Company
9%
Government
8%
Financial Services Firm
22%
Manufacturing Company
11%
Computer Software Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business28
Midsize Enterprise15
Large Enterprise56
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise22
 

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...
What do you like most about Jenkins?
Jenkins has been instrumental in automating our build and deployment processes.
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.
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...
What advice do you have for others considering Tekton?
I have been using Tekton for just one and a half years, so I should have more experience to provide comprehensive advice. I am just a user of Tekton and am not familiar with their pricing structure...
 

Comparisons

 

Overview

 

Sample Customers

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about Jenkins vs. Tekton and other solutions. Updated: February 2026.
881,733 professionals have used our research since 2012.