We performed a comparison between CircleCI 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."Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"The ability to automate the build process in a seamless way and run workflows effortlessly. It supports parallel builds so it can scale well. Also, it covers the basics of any build and integration tool, including email notifications (especially when tests are fixed), project insights, etc."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"It's a stable product."
"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"The solution offers continuous integration and continuous delivery."
"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."
"Integration with Microsoft Azure is one area for improvement. Azure is growing in its user base, and supports various cloud infrastructure components such as Service Fabric, App Service, etc. Some of Azure’s deployment models (like Kudu) require a steep learning curve, but if CircleCI would come up with such features (deployment to App Service) out of the box, it would be amazing."
"The solution’s pricing could be better."
"Billing is a mess."
"There needs to be some improvement in the user interface of CircleCI."
"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."
CircleCI is ranked 11th in Build Automation with 5 reviews while Tekton is ranked 4th in Build Automation with 3 reviews. CircleCI is rated 6.6, while Tekton is rated 6.4. The top reviewer of CircleCI writes "Unhelpful support, unclear billing, and has offers ability to track usage". 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 ". CircleCI is most compared with TeamCity, Jenkins, GitHub Actions, AWS CodeBuild and GoCD, whereas Tekton is most compared with GitLab, GitHub Actions, Harness, Travis CI and Bamboo. See our CircleCI 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.
