GNU Make vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
GNU Logo
230 views|189 comparisons
80% willing to recommend
Jenkins Logo
6,756 views|5,825 comparisons
88% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between GNU Make and Jenkins 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 GNU Make vs. Jenkins Report (Updated: May 2024).
771,157 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
"Setup is extremely straightforward.""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.""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.""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."

More GNU Make Pros →

"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available.""Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins.""It can scale easily.""Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases.""We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc.""With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it.""Has enabled full automation of the company.""The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."

More Jenkins 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 →

"Sometimes you have Jenkins restarting because of OOM errors.""The scriptwriting process could be improved in this solution in the future.""The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift.""They need to improve their documentation.""The learning curve is quite steep at the moment.""We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms.""It does not have a very user-friendly interface.""I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."

More Jenkins 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 →

  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    771,157 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: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 easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ranking
    25th
    out of 41 in Build Automation
    Views
    230
    Comparisons
    189
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    2nd
    out of 41 in Build Automation
    Views
    6,756
    Comparisons
    5,825
    Reviews
    37
    Average Words per Review
    382
    Rating
    7.9
    Comparisons
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 10% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    CircleCI logo
    Compared 3% 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.

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    Sample Customers
    Information Not Available
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    No Data Available
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    No Data Available
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    GNU Make vs. Jenkins
    May 2024
    Find out what your peers are saying about GNU Make vs. Jenkins and other solutions. Updated: May 2024.
    771,157 professionals have used our research since 2012.

    GNU Make is ranked 25th in Build Automation while Jenkins is ranked 2nd in Build Automation with 83 reviews. GNU Make is rated 8.2, while Jenkins is rated 8.0. 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 Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". GNU Make is most compared with Bazel, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and CircleCI. See our GNU Make vs. Jenkins 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.