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."The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"Jenkins is very stable."
"I like that you can find a wide range of plugins for Jenkins."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"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."
"Jenkins has a lot of built-in packages and tools."
"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."
"Very easy to understand for newcomers."
"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."
"It does not have a very user-friendly interface."
"Jenkins takes a long time to create archive files."
"It could be cheaper."
"Better and easy-to-use integration with Docker would be an improvement."
"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."
"Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"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 4 reviews. Jenkins is rated 8.0, while Tekton is rated 7.0. 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 "A pipeline tool to create CI integrations for applications with ease of use". 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.