TeamCity vs Tekton comparison

"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."

"TeamCity is more structured and user-friendly than other vendors."

"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."

"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."

"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."

"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."

"Good integration with IDE and JetBrains products."

"TeamCity is very useful due to the fact that it has a strong plug-in system."

"The tool offers flexibility and compatibility."

"When you run a pipeline, all the jobs are called. It is a very valuable feature that enhances job maintenance overall."

"I like the setup of the dashboard."

"One of the best things I appreciate is that Tekton runs on the Kubernetes platform. This is very useful when working on a project with other team members. For instance, suppose we have a very big project that requires building a large amount of source code or running many unit tests. During the build and unit test phases, Tekton on Kubernetes allows us to have a scalable machine to handle these tasks. This scalability is the most useful aspect for me."

"Tekton is a cloud-native solution. It offers optimal resource consumption, allowing tasks to be run more efficiently and at a lower cost."

"Tekton's inclusion in Kubernetes deployment offers better visibility on how Tekton is performing within a cluster. It is lightweight and not as heavy as Jenkins to maintain."

"The tool's most valuable aspect is its compatibility with the cloud-native environment. It can be easily installed on Kubernetes and leverages its resources to run CI/CD pipelines."

"The flexibility of Tekton is the most valuable feature"

"I need some more graphical design."

"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."

"The integration between other solutions and TeamCity could be smoother."

"I would like to see an improvement where TeamCity alerts us via email or another medium if there are discrepancies between the code in the staging environment and what has been deployed to production, such as missing updates."

"The upgrade process could be smoother. Upgrading major versions can often cause some pain."

"It will benefit this solution if they keep up to date with other CI/CD systems out there."

"REST API support lacks many features in customization of builds, jobs, and settings."

"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."

"The stability issues can be there."

"Initially, working with YAML configuration can be challenging using the solution."

"The product's scalability can be challenging when multiple users access it simultaneously."

"For infrastructure deployment, integration is somewhat complex, especially when using Terraform with Tekton. It would be beneficial if this process were simplified."

"If you are a beginner, then accessing the flexibility part can be overwhelming. We think the learning curve of the tool is steep, especially for those who are not already familiar with Kubernetes."

"There might be occasional issues with storage or cluster-level logging, which can affect production."

"The user interface of Tekton could be improved."

"The product's version update management process needs improvement."

"The licensing is on an annual basis."

"Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."

"The tool is open-source and free to use."

"The solution is open-source."

"It is entirely open source and free of charge."

"Tekton is an open-source tool."

"The product is free and open-source."

"The product is free of cost."