Try our new research platform with insights from 80,000+ expert users

TeamCity vs Tekton comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

TeamCity
Ranking in Build Automation
10th
Average Rating
8.2
Number of Reviews
28
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
2nd
Average Rating
7.6
Number of Reviews
36
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Build Automation category, the mindshare of TeamCity is 7.3%, up from 6.8% compared to the previous year. The mindshare of Tekton is 12.1%, up from 10.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Omakoji Idakwoji - PeerSpot reviewer
Build management system used to successfully create full request tests and run security scans
I find the TeamCity backend easily accessible. Users can login to the Linux servers that TeamCity is installed on and perform operations. Also I find the ability to template solutions using the meta runner a good feature as well as the user management feature. There is a display that shows which user made recent changes to a branch on GitHub, including the time the changes were made and the particular agent that ran the job. This is also a very useful feature. The metrics and audit available for projects, pipelines and jobs come in handy when debugging.
AjayKrishna - PeerSpot reviewer
If you're dealing with many applications and need a reliable, scalable, and efficient system, I'd recommend this solution
Tekton's most important feature is its cloud-native nature. Unlike Jenkins, which may not scale as efficiently, Tekton's CI pipeline can automatically scale up to handle increased workload demands without needing manual adjustments. Another important aspect is the level of customization offered by Tekton. Each task in the CI pipeline can be customized independently, allowing developers to write code in various languages like shell scripting, Java, or Python and incorporate them into the pipeline as needed. This level of abstraction and customization greatly benefits developers in creating efficient CI pipelines. Also, it can be challenging to understand the logs and troubleshoot issues without clear guidance. It's not always easy to reach technical support and get immediate answers. In my opinion, improvement in this area would be beneficial.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"TeamCity's GUI is nice."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"Good integration with IDE and JetBrains products."
"The integration is a valuable feature."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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."
"TeamCity is more structured and user-friendly than other vendors."
"We just have some configuration files, and it will handle the deployments smoother and faster compared to CI/CD 2.0."
"I like the branching and visualization tools for the pipeline."
"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."
"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 installation process is seamless, requiring fewer resources compared to Jenkins."
"Tekton provides a feature where you can schedule the job."
"The feature that I like most about Tekton is that it is built for Kubernetes, so we can utilize our resources effectively."
"Tekton has a user interface that facilitates time savings, making it more user-friendly than Jenkins."
 

Cons

"If there was more documentation that was easier to locate, it would be helpful for users."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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."
"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."
"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 upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline."
"Compared to traditional tools like Jenkins, Tekton lacks a lot of features. It's not efficient in managing conflicts between multiple pipelines."
"The product's scalability can be challenging when multiple users access it simultaneously."
"One area where Tekton can improve is log management."
"Tekton is a good product with all the features I need. There isn't anything that needs improvement."
"Tekton lacks sufficient documentation"
"Initially, working with YAML configuration can be challenging using the solution."
"The product's version update management process needs improvement."
 

Pricing and Cost Advice

"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 product is free of cost."
"The product is free and open-source."
"The solution is open-source."
"It is entirely open source and free of charge."
"Tekton is an open-source tool."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
831,020 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis…
 

Top Industries

By visitors reading reviews
Financial Services Firm
27%
Computer Software Company
17%
Manufacturing Company
7%
Government
5%
Financial Services Firm
22%
Manufacturing Company
15%
Computer Software Company
13%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about TeamCity?
One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.
What is your experience regarding pricing and costs for TeamCity?
Compared to new technologies, TeamCity is more expensive and is an older tool compared to tools like GitLab.
What needs improvement with TeamCity?
TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related ...
How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What do you like most about Tekton?
Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively.
What needs improvement with Tekton?
Regarding areas for improvement in Tekton, I have not encountered significant issues. It works well for our use case. However, incorporating AI could be a potential enhancement in the future.
 

Comparisons

 

Learn More

 

Overview

 

Sample Customers

Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about TeamCity vs. Tekton and other solutions. Updated: January 2025.
831,020 professionals have used our research since 2012.