Jenkins vs Tekton comparison

Jenkins and Google are both solutions in the Build Automation category. Jenkins is ranked #3 with an average rating of 8.1, while Google is ranked #2 with an average rating of 7.8. Jenkins holds a 10.6% mindshare in BA, compared to Google’s 12.1% mindshare. Additionally, 87% of Jenkins users are willing to recommend the solution, compared to 88% of Google users who would recommend it.

Jenkins

Read 93 Jenkins reviews

4,377 Views
3,762 Comparison Views

87% willing to recommend

Tekton

Read 36 Tekton reviews

5,137 Views
3,266 Comparison Views

88% willing to recommend

Jenkins

Tekton

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Mar 5, 2025

Jenkins and Tekton are prominent competitors in the CI/CD tool category. Jenkins, with its extensive plugin ecosystem and strong community support, holds the advantage for customization. Tekton, however, has the edge in Kubernetes-native environments due to its seamless cloud-native integration.

Features: Jenkins provides a massive plugin ecosystem, pipeline integration capabilities, and scalability across various use cases. Tekton excels with its Kubernetes-native design enabling container-based application flexibility, efficient CI/CD pipeline management, and seamless scalability within cloud environments.

Room for Improvement: Jenkins could improve its user interface, plugin stability, and support better cloud integration documentation. Tekton needs to enhance its deployment accessibility, standardize template creation, and improve YAML configuration management.

Ease of Deployment and Customer Service: Jenkins offers diverse deployment options, including on-premises and various cloud settings, but often needs internal expertise for troubleshooting. Community support is robust but lacks formal customer service. Tekton suits hybrid and cloud settings well, aligning with Kubernetes, which demands more cloud-native configuration expertise.

Pricing and ROI: Jenkins is open-source, providing free access but requiring management for add-ons, leading to cost savings through automation. Tekton, also free and open-source, offers additional savings through resource-efficient management and integration with platforms like Kubernetes, enhancing ROI by reducing operational costs.

To learn more, read our detailed Jenkins vs. Tekton Report (Updated: March 2025).

Buyer's Guide

Jenkins vs. Tekton

March 2025

Download the complete report

Helped 842,194 peers since 2012

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

3rd

Average Rating

8.0

Reviews Sentiment

7.0

Number of Reviews

Ranking in other categories

No ranking in other categories

Tekton

Ranking in Build Automation

2nd

Average Rating

7.6

Reviews Sentiment

7.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of March 2025, in the Build Automation category, the mindshare of Jenkins is 10.6%, down from 14.0% compared to the previous year. The mindshare of Tekton is 12.1%, up from 10.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Dinesh-Patil

Consultant at a manufacturing company with 10,001+ employees

A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment

The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.

Read full review

AjayKrishna

Senior Software Engineer at a transportation company with 10,001+ employees

If you're dealing with many applications and need a reliable, scalable, and efficient system, I'd recommend this solution

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. Another important aspect is the level of customization offered by Tekton. Each task in the CI pipeline can be customized independently, allowing developers to write code in various languages like shell scripting, Java, or Python and incorporate them into the pipeline as needed. This level of abstraction and customization greatly benefits developers in creating efficient CI pipelines. Also, it can be challenging to understand the logs and troubleshoot issues without clear guidance. It's not always easy to reach technical support and get immediate answers. In my opinion, improvement in this area would be beneficial.

Read full review

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."

"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."

"Jenkins is very customizable."

"It offers continuous deployment and continuous testing. It enables us to figure out anything."

"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's very useful when you want to automate different processes from beginning to end."

"We used it for all continuous integration parts, like automation testing, deployment, etc."

"The initial setup is simple."

More Jenkins pros

"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 would say the customization ability that Tekton provides is good."

"The platform's most valuable feature is its cloud-native and Kubernetes-ready design."

"When you run a pipeline, all the jobs are called. It is a very valuable feature that enhances job maintenance overall."

"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."

"The feature that I like most about Tekton is that it is built for Kubernetes, so we can utilize our resources effectively."

"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."

"The platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow."

More Tekton pros

Cons

"Centralized user management would be helpful."

"Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests."

"Jenkins takes a long time to create archive files."

"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."

"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."

"The UI must be more user-friendly."

"The learning curve is quite steep at the moment."

"The UI of Jenkins could improve."

More Jenkins cons

"Improvement is needed in the build step."

"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."

"The product's UI could be improved, as there are occasional latency issues. The triggering part, especially the CRD installation needs enhancement."

"The product's version update management process needs improvement."

"I'm a bit worried about scaling Tekton from the point of view of big CI/CD processes."

"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."

"Tekton should include many features to integrate event-driven pipelines."

"RBAC is really needed for Tekton."

More Tekton cons

Pricing and Cost Advice

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"Jenkins is open-source, so it is free."

"I used the free OSS version all the time. It was enough for all my needs."

"Some of the add-ons are too expensive."

"Jenkins is a free open-source server."

"It is free."

"Jenkins is open source."

"It is a free product."

More Jenkins pricing and cost advice

"The product is free of cost."

"It is entirely open source and free of charge."

"The product is free and open-source."

"The solution is open-source."

"Tekton is an open-source tool."

"The tool is open-source and free to use."

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

842,194 professionals have used our research since 2012.

Comparison Review

it_user184734

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…

Read full review

Top Industries

By visitors reading reviews

Financial Services Firm

22%

Computer Software Company

17%

Manufacturing Company

11%

Government

Financial Services Firm

23%

Manufacturing Company

13%

Computer Software Company

12%

Government

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

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...

See all answers

What do you like most about Jenkins?

Jenkins has been instrumental in automating our build and deployment processes.

See all answers

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.

See all answers

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.

See all answers

What needs improvement with Tekton?

Regarding areas for improvement in Tekton, I have not encountered significant issues. It works well for our use case. However, incorporating AI could be a potential enhancement in the future.

See all answers

What is your primary use case for Tekton?

Tekton is used as a Kubernetes native tool for creating CI/CD pipelines. It is used for creating multiple tasks that can run as pipeline runs for several services. This helps in reducing time wasta...

See all answers

Comparisons

GitLab vs Jenkins

Compared 15% of the time

Harness vs Jenkins

Compared 14% of the time

Bamboo vs Jenkins

Compared 9% of the time

Bazel vs Jenkins

Compared 9% of the time

AWS CodePipeline vs Jenkins

Compared 6% of the time

More Jenkins Competitors

GitHub Actions vs Tekton

Compared 34% of the time

GitLab vs Tekton

Compared 25% of the time

Harness vs Tekton

Compared 8% of the time

Bamboo vs Tekton

Compared 6% of the time

CircleCI vs Tekton

Compared 6% of the time

More Tekton Competitors

Product Reports

Buyer's Guide

Jenkins

March 2025

Download Jenkins product report

Buyer's Guide

Tekton

March 2025

Download Tekton product report

Overview

Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

Jenkins

Tekton is a powerful yet flexible Kubernetes-native open-source framework for creating continuous integration and delivery (CI/CD) systems. It lets you build, test, and deploy across multiple cloud providers or on-premises systems by abstracting away the underlying implementation details.

Google

Sample Customers

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox

The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture

Buyer's Guide

Jenkins vs. Tekton

March 2025

Free Report: Jenkins vs. Tekton

Find out what your peers are saying about Jenkins vs. Tekton and other solutions. Updated: March 2025.

DOWNLOAD NOW

842,194 professionals have used our research since 2012.

See our Jenkins vs. Tekton report.

See our list of best Build Automation vendors.

We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.