Incredibuild vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
IncrediBuild Logo
677 views|322 comparisons
100% willing to recommend
JetBrains Logo
3,373 views|2,977 comparisons
92% willing to recommend
Comparison Buyer's Guide
Executive Summary

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

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: April 2024).
767,847 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 is saving time for developers, which is saving money for the company."

More Incredibuild Pros →

"It's easy to move to a new release because of templates and meta-runners, and agent pooling.""TeamCity is very useful due to the fact that it has a strong plug-in system.""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.""TeamCity's GUI is nice.""Good integration with IDE and JetBrains products.""It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack.""We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."

More TeamCity Pros →

Cons
"Stability could be improved. I don't know the reason for the instability because there are no logs that help me to understand the problem."

More Incredibuild Cons →

"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 upgrade process could be smoother. Upgrading major versions can often cause some pain.""REST API support lacks many features in customization of builds, jobs, and settings.""If there was more documentation that was easier to locate, it would be helpful for users.""It will benefit this solution if they keep up to date with other CI/CD systems out there.""I need some more graphical design.""Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity.""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."

More TeamCity Cons →

Pricing and Cost Advice
  • "Its pricing and licensing are annoying. Every year, I need to renew. If I miss the deadline date, all my processes will stop working. So, I would prefer that I wouldn't need to renew every year, instead have another solution for it. Or, if we could have an enterprise license agreement with the company, then the development team wouldn't need to spend time renewing licenses."
  • More Incredibuild 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."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    767,847 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
    Ask a question

    Earn 20 points

    Top Answer:TeamCity is a very user-friendly tool.
    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:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it or to optimize it. As a user, I need some more graphical design. For example, in… more »
    Ranking
    20th
    out of 41 in Build Automation
    Views
    677
    Comparisons
    322
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    6th
    out of 41 in Build Automation
    Views
    3,373
    Comparisons
    2,977
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    Bazel logo
    Compared 56% of the time.
    Jenkins logo
    Compared 14% of the time.
    GitLab logo
    Compared 12% of the time.
    GitLab logo
    Compared 45% of the time.
    CircleCI logo
    Compared 17% of the time.
    Jenkins logo
    Compared 9% of the time.
    Harness logo
    Compared 6% of the time.
    Travis CI logo
    Compared 1% of the time.
    Learn More
    Overview

    Incredibuild, the world’s leading platform for development acceleration, lets you deliver faster developer cycles and shorten your time-top market with more compute power and lower costs on prem and the cloud.

    Incredibuild enables every machine to use hundreds of cores to accelerate time-consuming software development by using idle CPUs in network or bursting to the cloud. Use the full potential of your network to raise product quality, iterate more frequently, and increase dev productivity.

    Most importantly, Incredibuild works out of the box, no need to change any of your existing toolchain, processes, or code.

    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
    Over 2,000 companies worldwide across industries inluding Epic Games, Microsoft, Playstation, Nintendo, Samsung, GM, Intel, CitiGroup, Qualcomm, Boeing, Motorola, Qt, and more accelerate their development and enhance their devs’ productivity with Incredibuild.
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    VISITORS READING REVIEWS
    Manufacturing Company19%
    Computer Software Company15%
    Legal Firm10%
    Non Profit7%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Leisure / Travel Company7%
    Non Tech Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company9%
    Comms Service Provider7%
    Company Size
    VISITORS READING REVIEWS
    Small Business21%
    Midsize Enterprise18%
    Large Enterprise61%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise66%
    Buyer's Guide
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: April 2024.
    767,847 professionals have used our research since 2012.

    Incredibuild is ranked 20th in Build Automation while TeamCity is ranked 6th in Build Automation with 25 reviews. Incredibuild is rated 8.0, while TeamCity is rated 8.2. The top reviewer of Incredibuild writes "Saves time for developers, which saves money for the company". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Incredibuild is most compared with Bazel, Jenkins and GitLab, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and Travis CI.

    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.