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.4% mindshare in BA, compared to Google’s 12.3% 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,156 Views
3,557 Comparison Views

87% willing to recommend

Tekton

Read 36 Tekton reviews

4,811 Views
3,186 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 845,040 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 April 2025, in the Build Automation category, the mindshare of Jenkins is 10.4%, down from 13.8% compared to the previous year. The mindshare of Tekton is 12.3%, up from 10.6% 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

"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."

"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."

"I like the business logs. It's a very useful tool. Client-server communication is also very fast."

"GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins."

"The deployment of traditional Jenkins is easy."

"The most valuable feature is its ability to connect with different tools and technologies."

"Jenkins is very stable."

"Distributed execution of build and test jobs."

More Jenkins pros

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

"The installation process is seamless, requiring fewer resources compared to Jenkins."

"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."

"The product's best feature is its ease of implementation."

"It is an open-source tool, which makes it highly adaptable."

"Tekton has a user interface that facilitates time savings, making it more user-friendly than Jenkins."

"Tekton is an orchestrator. It provides seamless integration for our pipelines. It offers robust support for executing tasks within the pipeline, allowing us to set up and run pipelines quickly."

"The flexibility of Tekton is the most valuable feature"

More Tekton pros

Cons

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

"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."

"It can be improved by including automated mobile reporting integrations."

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

"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."

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

"Better and easy-to-use integration with Docker would be an improvement."

More Jenkins cons

"The product's scalability can be challenging when multiple users access it simultaneously."

"For infrastructure deployment, integration is somewhat complex, especially when using Terraform with Tekton. It would be beneficial if this process were simplified."

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

"Initially, working with YAML configuration can be challenging using the solution."

"One area for improvement is the number of CRDs created during installation. Tekton currently creates 10 to 11 CRDs, which can be overwhelming."

"Tekton lacks integration capabilities compared to other CI/CD tools like Jenkins and Travis."

"The product's documentation is an area of concern, making it an area where improvements are required."

"There might be occasional issues with storage or cluster-level logging, which can affect production."

More Tekton cons

Pricing and Cost Advice

"Jenkins is an open-source platform."

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"The tool is open-source."

"Jenkins is a free open-source server."

"The solution is one of the lowest costs compared to competitors."

"We are using the freeware version of Jenkins."

"There is no cost. It is open source."

"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."

More Jenkins pricing and cost advice

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

"Tekton is an open-source tool."

"The product is free of cost."

"The product is free and open-source."

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

"The solution is open-source."

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

845,040 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

24%

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

Bazel vs Jenkins

Compared 9% of the time

Bamboo vs Jenkins

Compared 9% of the time

AWS CodePipeline vs Jenkins

Compared 6% of the time

More Jenkins Competitors

GitHub Actions vs Tekton

Compared 33% 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

845,040 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.