We performed a comparison between Inedo BuildMaster and Jenkins based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation."Technical support is quick to respond. I haven't had any issues with them."
"Jenkins is very stable."
"The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"Distributed execution of build and test jobs."
"When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams."
"A lot of support material exists via a single web search of exactly what you're looking for."
"The automated elements are easy to use and you can put them into your server."
"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."
"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."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
"Centralized user management would be helpful."
"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."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"The solution's UI can use a facelift and the logs can use more detailed information."
"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
Inedo BuildMaster is ranked 21st in Build Automation with 1 review while Jenkins is ranked 2nd in Build Automation with 83 reviews. Inedo BuildMaster is rated 6.0, while Jenkins is rated 8.0. The top reviewer of Inedo BuildMaster writes "Deployment agent that allows us to deploy out to various other servers but doesn't provide build automation". 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". Inedo BuildMaster is most compared with , 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.