GNU Make vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
GNU Logo
226 views|183 comparisons
80% 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 GNU Make 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
"Full-featured syntax allows building strategies as simple or as complex as one wishes, and declarative approach fits the task really well. Wide adoption also means that everybody knows what GNU Make is and how to use it.""GNU Make is such an essential tool that it is almost impossible to imagine working without it. Not having it, developers would probably have to resort to doing everything manually or via shell scripts.""I have not encountered any scalability issues with GNU Make. It is as scalable as the project's structure is, and then some.""Setup is extremely straightforward.""Makefiles are extremely easy to work with using any preferred editor. GNU Make can be run directly from the terminal, not requiring any time wasted on clicking."

More GNU Make Pros →

"VCS Trigger: Provides excellent source control support.""The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine.""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 is very useful due to the fact that it has a strong plug-in system.""TeamCity's GUI is nice.""TeamCity is a very user-friendly tool.""Good integration with IDE and JetBrains products.""Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."

More TeamCity Pros →

Cons
"Vanilla GNU Make does not support any kind of colored output. A wrapper named colormake exists to work around this, but native (opt-in) support would be welcome.""GNU Make requires using the Tab symbol as the first symbol of command line for execution. In some text editors this can be problematic, as they automatically insert spaces instead of tabs."

More GNU Make Cons →

"REST API support lacks many features in customization of builds, jobs, and settings.""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 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.""It will benefit this solution if they keep up to date with other CI/CD systems out there.""I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.""I need some more graphical design.""Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."

More TeamCity Cons →

Pricing and Cost Advice
  • "There is no price for this product. No licensing. It’s open-source."
  • "GNU Make is free and open source software."
  • More GNU Make 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
    26th
    out of 41 in Build Automation
    Views
    226
    Comparisons
    183
    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
    Jenkins logo
    Compared 69% of the time.
    Bazel logo
    Compared 31% 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.
    Tekton logo
    Compared 6% of the time.
    Learn More
    Overview
    Make is a tool which controls the generation of executables and other non-source files of a program from the program's source files.

    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
    Information Not Available
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    No Data Available
    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
    No Data Available
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise65%
    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.

    GNU Make is ranked 26th in Build Automation while TeamCity is ranked 6th in Build Automation with 25 reviews. GNU Make is rated 8.2, while TeamCity is rated 8.2. The top reviewer of GNU Make writes "Full-featured syntax allows building strategies as simple or as complex as needed". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". GNU Make is most compared with Jenkins and Bazel, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness 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.