GNU Make vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
GNU Logo
226 views|183 comparisons
80% willing to recommend
Jenkins Logo
6,896 views|5,921 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 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).
768,886 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
"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.""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.""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 →

"The solution is scalable and has a large number of plugins that can help you scale it to your needs.""Jenkins is very user-friendly.""We used it for all continuous integration parts, like automation testing, deployment, etc.""The solution is scalable and concurrent users have access to the platform.""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.""We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable.""Jenkins has built good plugins and has a good security platform.""It is a stable solution."

More Jenkins Pros →

Cons
"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.""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."

More GNU Make Cons →

"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams.""This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager).""The UI of Jenkins could improve.""Partition security for the workflow of projects is not yet an option.""There are some difficulties when we need to execute the DB script.""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.""I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it.""Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."

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.
    768,886 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
    26th
    out of 41 in Build Automation
    Views
    226
    Comparisons
    183
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    2nd
    out of 41 in Build Automation
    Views
    6,896
    Comparisons
    5,921
    Reviews
    39
    Average Words per Review
    386
    Rating
    7.8
    Comparisons
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 9% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Tekton logo
    Compared 7% 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 Firm20%
    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
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: April 2024.
    768,886 professionals have used our research since 2012.

    GNU Make is ranked 26th 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 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.