Harness vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Harness Logo
2,387 views|1,869 comparisons
100% willing to recommend
JetBrains Logo
3,337 views|2,954 comparisons
92% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Harness and TeamCity based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: May 2024).
771,212 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"It's a highly customizable DevOps tool."

More Harness Pros →

"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.""TeamCity is very useful due to the fact that it has a strong plug-in system.""We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted.""TeamCity is a very user-friendly tool.""One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.""Good integration with IDE and JetBrains products.""The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."

More TeamCity Pros →

Cons
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."

More Harness 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.""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.""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.""I need some more graphical design.""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.""It will benefit this solution if they keep up to date with other CI/CD systems out there.""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."

More TeamCity Cons →

Pricing and Cost Advice
Information Not Available
  • "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."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    771,212 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    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 nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer: It's a highly customizable DevOps tool.
    Top Answer:The platform's initial setup process could be simplified. Additionally, security features and capabilities for understanding vulnerabilities within the application could be enhanced directly from the… more »
    Top Answer:We use Harness for deploying Kubernetes clusters. It is a SaaS-based tool with a good graphical user interface. We can create workflows and deployment pipelines and easily visualize them. We can see… more »
    Top Answer:One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without you being involved and having it and managed by them, there may be costs involved… more »
    Top Answer:I haven't faced many challenges or issues that I would like to see improved in TeamCity. As for deployment challenges, they are often tied to the specific technology being integrated with TeamCity. In… more »
    Ranking
    8th
    out of 41 in Build Automation
    Views
    2,387
    Comparisons
    1,869
    Reviews
    1
    Average Words per Review
    376
    Rating
    7.0
    6th
    out of 41 in Build Automation
    Views
    3,337
    Comparisons
    2,954
    Reviews
    3
    Average Words per Review
    531
    Rating
    7.3
    Comparisons
    Tekton logo
    Compared 22% of the time.
    Jenkins logo
    Compared 20% of the time.
    Bamboo logo
    Compared 15% of the time.
    GitHub Actions logo
    Compared 10% of the time.
    GitLab logo
    Compared 7% of the time.
    GitLab logo
    Compared 44% of the time.
    CircleCI logo
    Compared 16% of the time.
    Jenkins logo
    Compared 8% of the time.
    GitHub Actions logo
    Compared 6% of the time.
    Tekton logo
    Compared 6% of the time.
    Also Known As
    Armory
    Learn More
    Harness
    Video Not Available
    Overview

    Harness offers a comprehensive toolset for automating deployment processes and enhancing software update efficiency. It's lauded for its CI/CD capabilities, feature flagging, and real-time deployment monitoring. Key features include an intuitive UI, secret management, and robust rollback functionalities, all contributing to improved productivity and reduced errors in DevOps environments.

    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.

    Sample Customers
    Linedata, Openbank, Home Depot, Advanced
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    VISITORS READING REVIEWS
    Financial Services Firm37%
    Computer Software Company12%
    Manufacturing Company6%
    Healthcare Company5%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Leisure / Travel Company7%
    Non Tech Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company10%
    Comms Service Provider7%
    Company Size
    VISITORS READING REVIEWS
    Small Business15%
    Midsize Enterprise8%
    Large Enterprise77%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise10%
    Large Enterprise65%
    Buyer's Guide
    Build Automation
    May 2024
    Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation. Updated: May 2024.
    771,212 professionals have used our research since 2012.

    Harness is ranked 8th in Build Automation with 1 review while TeamCity is ranked 6th in Build Automation with 25 reviews. Harness is rated 7.0, while TeamCity is rated 8.2. The top reviewer of Harness writes "Provides a good graphical interface, but the initial setup process needs improvement ". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Harness is most compared with Tekton, Jenkins, Bamboo, GitHub Actions and GitLab, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, GitHub Actions and Tekton.

    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.