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 September 2025, in the Build Automation category, the mindshare of Jenkins is 9.1%, down from 11.8% compared to the previous year. The mindshare of Tekton is 9.9%, 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.9%
Jenkins9.1%
Other81.0%
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…
Prasad Gupta - PeerSpot reviewer
Efficient CI/CD management with significant cost reduction and a user-friendly setup
One area for improvement is the number of CRDs created during installation. Tekton currently creates 10 to 11CRDs, which can be overwhelming. Instead, it would be better to have just one CRD that can handle all the information and create other necessary components automatically. Additionally, more integration capabilities for security, such as DAST, SAST, and IAST, should be directly built into Tekton to facilitate easier implementation of security features.

Quotes from Members

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

Pros

"Jenkins has excellent task planning features."
"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."
"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."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"Has a good interface, is reliable and saves time."
"Very easy to understand for newcomers."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"The initial setup is pretty simple."
"Tekton is highly customizable, with Kubernetes, we can customize on our own and create custom builders."
"The 'promote' feature is beneficial as it simplifies deployment processes by allowing easy promotion of applications to different environments without needing to re-run CI/CD processes."
"Tekton allows you to categorize tasks according to your needs and minimizes the amount of code needed."
"The platform's most valuable feature is its cloud-native and Kubernetes-ready design."
"The product's best feature is its ease of implementation."
"I like the setup of the dashboard."
"I would say the customization ability that Tekton provides is good."
"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."
 

Cons

"There is no way for the cloud repositories to trigger Jenkins."
"Logging could be improved to offer a clearer view."
"The UI of Jenkins could improve."
"The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."
"There are some issues with Jenkins, especially with the SIP job."
"A more user-friendly UI for creating pipelines would be helpful."
"Initially, working with YAML configuration can be challenging using the solution."
"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."
"Tekton is a good product with all the features I need. There isn't anything that needs improvement."
"The product's documentation is an area of concern, making it an area where improvements are required."
"The product's version update management process needs improvement."
"One area where Tekton can improve is log management."
"It would be better if Tekton could show the YAML file while it is running, similar to GitHub pipelines, to provide more visibility on what's happening."
"Tekton could improve by adding better documentation."
 

Pricing and Cost Advice

"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
"There is no cost. It is open source."
"It is an open source."
"Jenkins is open source."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"Jenkins is not expensive and reasonably priced."
"The tool is open-source."
"The solution is one of the lowest costs compared to competitors."
"The tool is open-source and free to use."
"Tekton is an open-source tool."
"It is entirely open source and free of charge."
"The solution is open-source."
"The product is free of cost."
"The product is free and open-source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
867,497 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
21%
Manufacturing Company
13%
Computer Software Company
13%
Government
7%
Financial Services Firm
20%
Manufacturing Company
13%
Computer Software Company
10%
Government
8%
 

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.
867,497 professionals have used our research since 2012.