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 has been instrumental in automating our build and deployment processes."
"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."
"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"Jenkins has built good plugins and has a good security platform."
"It is easy to use."
"Jenkins's open-based framework is very valuable."
"The most valuable feature of the solution is its integration between different tools."
"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."
"The flexibility of Tekton is the most valuable feature"
"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."
"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."
"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."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
"Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."
"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."
"A more user-friendly UI for creating pipelines would be helpful."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
"Tekton lacks sufficient documentation"
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
"I'm a bit worried about scaling Tekton from the point of view of big CI/CD processes."
"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 6 reviews. Jenkins is rated 8.0, while Tekton is rated 7.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 "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 Bazel, 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.
