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."
"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."
"It is easy to use."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
"The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"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."
"The documentation should be better. It should be very easy to call REST APIs, and the documentation has to be perfect for that."
"The bug fix speed is very slow."
"The enterprise version is less stable than the open-source version."
"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."
"Better and easy-to-use integration with Docker would be an improvement."
"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."
"Some kind of SaaS product would be helpful in providing organizational structure."
"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."
"Sometimes you have Jenkins restarting because of OOM errors."
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.