We performed a comparison between Jenkins and Tekton based on real PeerSpot user reviews.
Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."
"It is a stable solution."
"There are a large number of plugins available for integration with third party systems."
"Has enabled full automation of the company."
"Having builds and test tasks triggered on commit helps not to break the product."
"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."
"The most valuable feature is its ability to connect with different tools and technologies."
"Tekton is serverless and runs on OpenShift, and we leverage Tekton to take full advantage of the Kubernetes features such as running and scaling the solution in PaaS."
"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."
"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."
"Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."
"The documentation is not helpful, as it is not user-friendly."
"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."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
"UI is quite outdated."
"Centralized user management would be helpful."
"The upgrades need improvement."
"The documentation on plugin development could be better: more examples. "
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
"There might be occasional issues with storage or cluster-level logging, which can affect production."
Jenkins is ranked 2nd in Build Automation with 83 reviews while Tekton is ranked 4th in Build Automation with 3 reviews. Jenkins is rated 8.0, while Tekton is rated 6.4. The top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". On the other hand, the top reviewer of Tekton writes "Provides seamless integration for pipelines, allowing easy setup and execution of tasks but working with YAML files in Tekton can be challenging to modify ". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Harness, whereas Tekton is most compared with GitLab, GitHub Actions, Harness, Travis CI and CircleCI. 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.