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

Jenkins vs Tekton comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Jenkins
Ranking in Build Automation
3rd
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
89
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
2nd
Average Rating
7.8
Number of Reviews
34
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the Build Automation category, the mindshare of Jenkins is 11.3%, down from 14.5% compared to the previous year. The mindshare of Tekton is 11.9%, up from 9.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

AllenUmlas - PeerSpot reviewer
Feb 29, 2024
Streamlines the CI/CD process with its user-friendly interface, extensive plugin ecosystem and efficient automation capabilities
In our CI/CD pipeline, we rely on Jenkins to trigger various tasks related to the Telco Cloud infrastructure. It's an essential tool for managing our infrastructure tasks efficiently Jenkins is incredibly user-friendly, so I haven't encountered any difficulties using it. It's the only product…
AjayKrishna - PeerSpot reviewer
May 29, 2024
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.

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 of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."
"It is easy to use."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"The initial setup is pretty simple."
"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"I like that you can find a wide range of plugins for Jenkins."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
"Has enabled full automation of the company."
"The feature that I like most about Tekton is that it is built for Kubernetes, so we can utilize our resources effectively."
"The flexibility of Tekton is the most valuable feature"
"The platform's most valuable feature is its cloud-native and Kubernetes-ready design."
"Tekton provides a feature where you can schedule the job."
"The installation process is seamless, requiring fewer resources compared to Jenkins."
"Tekton is a stable product."
"It scales automatically based on the number of tasks or pipelines running, which is efficient and effective for our development needs."
"It enables enterprises to build a flexible framework atop Tekton, making it easier to define workflows with standard inputs and outputs."
 

Cons

"Sometimes you have Jenkins restarting because of OOM errors."
"We cannot change the ownership of any directory or file or any kind of directory."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"The enterprise version is less stable than the open-source version."
"It does not have a very user-friendly interface."
"The documentation could be more friendly, and more examples of how to use it."
"In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS."
"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."
"The product's version update management process needs improvement."
"The user interface of Tekton could be improved."
"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."
"RBAC is really needed for Tekton."
"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."
"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."
"If you are a beginner, then accessing the flexibility part can be overwhelming. We think the learning curve of the tool is steep, especially for those who are not already familiar with Kubernetes."
 

Pricing and Cost Advice

"It could be cheaper because there are many solutions available in the market. We are paying yearly."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"We are using the free version of Jenkins. There are no costs or licensing."
"Jenkins is not expensive and reasonably priced."
"In our company, we do pay for the licensing of the solution."
"Jenkins is a free solution, it is open source."
"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."
"The solution is one of the lowest costs compared to competitors."
"The product is free and open-source."
"The tool is open-source and free to use."
"The solution is open-source."
"Tekton is an open-source tool."
"It is entirely open source and free of charge."
"The product is free of cost."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
815,854 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
23%
Computer Software Company
16%
Manufacturing Company
11%
Government
6%
Financial Services Firm
22%
Manufacturing Company
15%
Computer Software Company
12%
Government
9%
 

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...
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 open source and free to use. You simply download it, install it on your server, and it manages your pipelines.
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?
Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline.
What is your primary use case for Tekton?
I am using Tekton for continuous integration in our project.
 

Comparisons

 

Learn More

 

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: October 2024.
815,854 professionals have used our research since 2012.