Jenkins vs Tekton comparison

"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."

"Jenkins is particularly valuable since it saves time by automating manual tasks."

"Jenkins is a CI/CD tool and is the most robust tool."

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

"Jenkins is free and open source."

"The solution is scalable and concurrent users have access to the platform."

"Jenkins is very user-friendly."

"Jenkins is very easy to use."

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

"Tekton is a stable product."

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

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

"The ability to scale is valuable."

"It scales automatically based on the number of tasks or pipelines running, which is efficient and effective for our development needs."

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

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

"The upgrades need improvement."

"The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective."

"The documentation could be more friendly, and more examples of how to use it."

"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."

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

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

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

"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."

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

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

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

"While Tekton is highly effective for Kubernetes-based setups, it might not suit users who require more control over bare-metal environments."

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

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

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

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

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

"It's free software with a big community behind it, which is very good."

"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."

"Jenkins is an open-source platform."

"It could be cheaper because there are many solutions available in the market. We are paying yearly."

"Jenkins is an open-source tool."

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

"Jenkins is a free solution, it is open source."

"Tekton is an open-source tool."

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

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

"The product is free and open-source."

"The product is free of cost."

"The solution is open-source."