We performed a comparison between TeamCity 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."TeamCity's GUI is nice."
"The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
"Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end."
"The integration is a valuable feature."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"TeamCity is a very user-friendly tool."
"Good integration with IDE and JetBrains products."
"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."
"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."
"The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs."
"Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone) to provide training classes to help newcomers get things up and running more quickly."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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."
TeamCity is ranked 6th in Build Automation with 25 reviews while Tekton is ranked 3rd in Build Automation with 3 reviews. TeamCity is rated 8.2, while Tekton is rated 6.4. The top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". 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 ". TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and GitHub Actions, whereas Tekton is most compared with GitLab, GitHub Actions, Harness, Travis CI and Concourse for VMware Tanzu. See our TeamCity 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.
