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 initial setup is simple."
"Very easy to understand for newcomers."
"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."
"Jenkins' most valuable feature is Pipeline."
"It is a stable solution."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"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."
"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 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."
"The learning curve is quite steep at the moment."
"Partition security for the workflow of projects is not yet an option."
"The documentation on plugin development could be better: more examples. "
"Better and easy-to-use integration with Docker would be an improvement."
"Sometimes you have Jenkins restarting because of OOM errors."
"There are some difficulties when we need to execute the DB script."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"It would be helpful if they had a bit more interactive UI."
"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."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
Jenkins is ranked 2nd in Build Automation with 83 reviews while Tekton is ranked 3rd 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.
