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 October 2025, in the Build Automation category, the mindshare of Jenkins is 9.1%, down from 11.4% compared to the previous year. The mindshare of Tekton is 9.6%, down from 11.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Tekton9.6%
Jenkins9.1%
Other81.3%
Build Automation
 

Featured Reviews

Annamalai Pts - PeerSpot reviewer
Streamlined CI/CD pipelines with powerful integration and an easy setup
I use Jenkins as a CI/CD tool. We create pipelines using Jenkins, with stages for Maven builds, Docker image builds, SonarQube integration, and deploying the image to a Kubernetes cluster, AWS EKS Jenkins has made the developers' work very easy. They commit to the remote repository, and…
Pravar Agrawal - PeerSpot reviewer
Enhanced Kubernetes workflows with lightweight and declarative pipelines
I appreciate its declarative style, which is easier to operate compared to something like Jenkins. Tekton offers better control in writing different pipelines or workflows, and its style is easier to understand. Additionally, 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.

Quotes from Members

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

Pros

"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes."
"Jenkins is particularly valuable since it saves time by automating manual tasks."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"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 scales automatically based on the number of tasks or pipelines running, which is efficient and effective for our development needs."
"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 cloud-native solution. It offers optimal resource consumption, allowing tasks to be run more efficiently and at a lower cost."
"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 platform's most valuable feature is its cloud-native and Kubernetes-ready design."
"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."
"I find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."
 

Cons

"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"The learning curve is quite steep at the moment."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"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."
"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."
"The enterprise version is less stable than the open-source version."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
"Some kind of SaaS product would be helpful in providing organizational structure."
"The stability issues can be there."
"While Tekton is highly effective for Kubernetes-based setups, it might not suit users who require more control over bare-metal environments."
"Improvement is needed in the build step."
"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 should include many features to integrate event-driven pipelines."
"Tekton lacks sufficient documentation"
"The product's version update management process needs improvement."
"The tool should improve in terms of output flexibility. It runs on a specific Kubernetes machine, and the persistent memory storage is on a single partition. Improving this aspect could make analyzing logs and toolchain outputs from external tools easier."
 

Pricing and Cost Advice

"Jenkins is open source."
"Jenkins is open-source, so it is free."
"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."
"The solution is open source."
"Jenkins is not expensive and reasonably priced."
"Jenkins is an open-source platform."
"Jenkins is a free solution, it is open source."
"The tool is open-source and free to use."
"The product is free and open-source."
"The solution is open-source."
"It is entirely open source and free of charge."
"The product is free of cost."
"Tekton is an open-source tool."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
872,029 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
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
20%
Manufacturing Company
14%
Computer Software Company
12%
Government
7%
Financial Services Firm
21%
Manufacturing Company
13%
Computer Software Company
10%
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 do you like most about Tekton?
Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively.
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

 

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: September 2025.
872,029 professionals have used our research since 2012.