GNU Make vs Jenkins comparison

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

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

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

"The initial setup of GNU Make is straightforward."

"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."

"Jenkins has a lot of built-in packages and tools."

"This is a great integration tool and very powerful."

"The most valuable feature of the solution is its integration between different tools."

"It is a stable solution."

"This solution has helped us in automating the build and test process, reducing time."

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

"Jenkins has been instrumental in automating our build and deployment processes."

"GNU Make does not provide traditional customer support."

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

"UI is quite outdated."

"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."

"There are some difficulties when we need to execute the DB script."

"The learning curve is quite steep at the moment."

"In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS."

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

"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."

"They need to improve their documentation."

"GNU Make is free and open source software."

"There is no price for this product. No licensing. It’s open-source."

"Jenkins is open-source, so it is free."

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"In our company, we do pay for the licensing of the solution."

"It could be cheaper because there are many solutions available in the market. We are paying yearly."

"We are using the free version of Jenkins. There are no costs or licensing."

"Jenkins is a free open-source server."

"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."

"It is a free product."