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 very user-friendly."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"The initial setup is simple."
"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"Jenkins is very stable."
"This is a great integration tool and very powerful."
"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."
"Very easy to understand for newcomers."
"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."
"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."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"The scriptwriting process could be improved in this solution in the future."
"Jenkins takes a long time to create archive files."
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"The enterprise version is less stable than the open-source version."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
"There might be occasional issues with storage or cluster-level logging, which can affect production."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
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.