TeamCity vs Tekton comparison

JetBrains and Google are both solutions in the Build Automation category. JetBrains is ranked #10 with an average rating of 6.0, while Google is ranked #2 with an average rating of 7.6. JetBrains holds a 6.8% mindshare in BA, compared to Google’s 11.9% mindshare. Additionally, 90% of JetBrains users are willing to recommend the solution, compared to 88% of Google users who would recommend it.

TeamCity

Read 28 TeamCity reviews

2,643 Views
2,335 Comparison Views

90% willing to recommend

Tekton

Read 34 Tekton reviews

6,543 Views
3,672 Comparison Views

88% willing to recommend

TeamCity

Tekton

Comparison Buyer's Guide

Download the report

Executive Summary

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.

To learn more, read our detailed TeamCity vs. Tekton Report (Updated: October 2024).

Buyer's Guide

TeamCity vs. Tekton

October 2024

Download the complete report

Helped 815,854 peers since 2012

Categories and Ranking

TeamCity

Ranking in Build Automation

10th

Average Rating

8.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Tekton

Ranking in Build Automation

2nd

Average Rating

7.8

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of November 2024, in the Build Automation category, the mindshare of TeamCity is 6.8%, down from 7.0% compared to the previous year. The mindshare of Tekton is 11.9%, up from 9.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Omakoji Idakwoji

Software Engineer at Home Depot

Jul 25, 2022

Build management system used to successfully create full request tests and run security scans

We use it for running unit tests for merge requests on github. We also use it to build executable artifacts and also for running security scans Time to deployment has been reduced. It has helped in preventing us from deploying breaking changes into production. If the pipelines are configured…

Read full review

AjayKrishna

Senior Software Engineer at a transportation company with 10,001+ employees

May 29, 2024

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.

Read full review

Quotes from Members

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

Pros

"The integration is a valuable feature."

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

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

"TeamCity's GUI is nice."

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

"Good integration with IDE and JetBrains products."

"It's easy to move to a new release because of templates and meta-runners, and agent pooling."

More TeamCity pros

"It scales automatically based on the number of tasks or pipelines running, which is efficient and effective for our development needs."

"The platform's most valuable feature is its cloud-native and Kubernetes-ready design."

"The feature that I like most about Tekton is that it is built for Kubernetes, so we can utilize our resources effectively."

"The platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow."

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

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

"The flexibility of Tekton is the most valuable feature"

"I find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."

More Tekton pros

Cons

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

"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."

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

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

"I need some more graphical design."

"If there was more documentation that was easier to locate, it would be helpful for users."

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

More TeamCity cons

"Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline."

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

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

"I'm a bit worried about scaling Tekton from the point of view of big CI/CD processes."

"The product's UI could be improved, as there are occasional latency issues. The triggering part, especially the CRD installation needs enhancement."

"Compared to traditional tools like Jenkins, Tekton lacks a lot of features. It's not efficient in managing conflicts between multiple pipelines."

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

"It would be better if Tekton could show the YAML file while it is running, similar to GitHub pipelines, to provide more visibility on what's happening."

More Tekton cons

Pricing and Cost Advice

"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 licensing is on an annual basis."

"Tekton is an open-source tool."

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

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

"The solution is open-source."

"The product is free of cost."

"The product is free and open-source."

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

815,854 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

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…

Read full review

Top Industries

By visitors reading reviews

Financial Services Firm

28%

Computer Software Company

17%

Manufacturing Company

Government

Financial Services Firm

22%

Manufacturing Company

15%

Computer Software Company

12%

Government

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.

See all answers

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.

See all answers

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

See all answers

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

See all answers

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.

See all answers

What needs improvement with Tekton?

Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline.

See all answers

Comparisons

GitLab vs TeamCity

Compared 38% of the time

GitHub Actions vs TeamCity

Compared 16% of the time

CircleCI vs TeamCity

Compared 12% of the time

Harness vs TeamCity

Compared 10% of the time

Jenkins vs TeamCity

Compared 7% of the time

More TeamCity Competitors

GitHub Actions vs Tekton

Compared 32% of the time

GitLab vs Tekton

Compared 26% of the time

Harness vs Tekton

Compared 8% of the time

Bamboo vs Tekton

Compared 7% of the time

Travis CI vs Tekton

Compared 4% of the time

More Tekton Competitors

Product Reports

Buyer's Guide

TeamCity

October 2024

Download TeamCity product report

Buyer's Guide

Tekton

October 2024

Download Tekton product report

Learn More

JetBrains

Google

Overview

TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

Tekton is a powerful yet flexible Kubernetes-native open-source framework for creating continuous integration and delivery (CI/CD) systems. It lets you build, test, and deploy across multiple cloud providers or on-premises systems by abstracting away the underlying implementation details.

Sample Customers

Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia

The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture

Buyer's Guide

TeamCity vs. Tekton

October 2024

Free Report: TeamCity vs. Tekton

Find out what your peers are saying about TeamCity vs. Tekton and other solutions. Updated: October 2024.

DOWNLOAD NOW

815,854 professionals have used our research since 2012.

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.