GNU Make vs. TeamCity

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
GNU Make
Score 7.7 out of 10
N/A
GNU Make is an open source and free build automation tool.N/A
TeamCity
Score 7.9 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.N/A
Pricing
GNU MakeTeamCity
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
GNU MakeTeamCity
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details——
More Pricing Information
Best Alternatives
GNU MakeTeamCity
Small Businesses
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
Enterprises
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
GNU MakeTeamCity
Likelihood to Recommend
7.1
(2 ratings)
9.9
(18 ratings)
Performance
-
(0 ratings)
9.3
(2 ratings)
Support Rating
7.1
(2 ratings)
-
(0 ratings)
User Testimonials
GNU MakeTeamCity
Likelihood to Recommend
Open Source
GNU Make is a great tool for simple builds where language-specific options are not available, or to provide shortcuts for common commands (e.g., "make build" as shorthand for "go build ..." with a bunch of flags). However, it is complementary to other build systems. It does not replace them, which is perhaps one of its greatest strengths as well (works with existing ecosystem instead of trying to do everything). GMU Make it simple to get started with, and the philosophy of understanding how sources map to outputs, as well as the dependency graph, are beneficial.
Read full review
JetBrains
TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.
Read full review
Pros
Open Source
  • Performance and accuracy of cross-module dependencies.
  • Simple to write and easy to understand.
Read full review
JetBrains
  • TeamCity provides a great integration with git, especially Bitbucket.
  • When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
  • TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.
Read full review
Cons
Open Source
  • No dependency management tools (but there are no cross-platform tools of this type anyway)
  • Tedious to do cross-compilation (Debug & Release builds, 32- and 64-bit builds, x86/ARM builds)
Read full review
JetBrains
  • The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
  • Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.
Read full review
Performance
Open Source
No answers on this topic
JetBrains
TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.
Read full review
Support Rating
Open Source
In general, it is fair to say the support is sufficient although we do not deal with support directly. There are a lot of forum people chiming in with suggestions or recommendations of particular usage or issues we run into. Since it is open software, patch and fixes will be available from time to time. A lot of information is available in the web now for knowing GNU Make from learning, example, teaching, etc.
Read full review
JetBrains
No answers on this topic
Alternatives Considered
Open Source
I'm a full-stack developer that has used various build tools, including Maven, Gradle, and NPM/yarn. For our C projects, I also investigated CMake and Ninja, but they seemed more difficult to learn and more tedious to work with. GNU Make is a single binary that can be easily downloaded, even for Windows under MingW32, is straightforward to learn, and works pretty well despite its age.
Read full review
JetBrains
TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud. VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only. TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
Read full review
Return on Investment
Open Source
  • Streamline the build based on a lot of existing component being done, reusable.
  • Commonly understandable, therefore, rampup effort is small.
Read full review
JetBrains
  • TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
  • TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
  • TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.
Read full review
ScreenShots