Jenkins vs Tekton comparison

"Jenkins has a lot of built-in packages and tools."

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

"Jenkins' most valuable feature is Pipeline."

"When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams."

"It is very useful for us to be able to collect and manage automatic processing pipelines."

"Jenkins is very user-friendly."

"I like that you can find a wide range of plugins for 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 platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow."

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

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

"One of the best things I appreciate is that Tekton runs on the Kubernetes platform. This is very useful when working on a project with other team members. For instance, suppose we have a very big project that requires building a large amount of source code or running many unit tests. During the build and unit test phases, Tekton on Kubernetes allows us to have a scalable machine to handle these tasks. This scalability is the most useful aspect for me."

"Tekton allows you to categorize tasks according to your needs and minimizes the amount of code needed."

"We can make a lot of customizations, and data sharing between tasks using workspaces is very convenient."

"It enables enterprises to build a flexible framework atop Tekton, making it easier to define workflows with standard inputs and outputs."

"The ability to scale is valuable."

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

"I would like to see even more integrations included in the next release."

"UI is quite outdated."

"Jenkins can sometimes run slow, especially when restarting after a plugin installation or when returning from a pipeline view to the dashboard."

"Support should be provided at no cost, as there is no free support available for any of the free versions."

"We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions."

"We cannot change the ownership of any directory or file or any kind of directory."

"There are some difficulties when we need to execute the DB script."

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

"The stability issues can be there."

"One area where Tekton can improve is log management."

"Tekton is a good product with all the features I need. There isn't anything that needs improvement."

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

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

"Compared to traditional tools like Jenkins, Tekton lacks a lot of features. It's not efficient in managing conflicts between multiple pipelines."

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

"​It is free.​"

"Jenkins is a free open-source server."

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

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

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

"In our company, we do pay for the licensing of the solution."

"It is a free product."

"The pricing for Jenkins is free."

"The product is free of cost."

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

"The product is free and open-source."

"Tekton is an open-source tool."

"The solution is open-source."

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