We performed a comparison between IBM Rational Build Forge 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."All features are useful. Our customer doesn't have any complaints about the tool. It works pretty well for what they want and what they need to do."
"Very good reporting features."
"Jenkins is very stable."
"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."
"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."
"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."
"The automated elements are easy to use and you can put them into your server."
"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."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"Jenkins' most valuable feature is Pipeline."
"Its logging can be improved. When something goes wrong, it is not always very easy to find the problem. It is hard to identify whether the problem is because of low memory in the server or some configuration in Rational Build Forge. The error logs are not very detailed, and they should provide more information. It should also have more integration with third-party tools. It would be great to have more integration with third-party tools."
"Not user friendly for the layman."
"Partition security for the workflow of projects is not yet an option."
"The documentation could be more friendly, and more examples of how to use it."
"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
"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."
"UI is quite outdated."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"We cannot change the ownership of any directory or file or any kind of directory."
"It could be cheaper."
Earn 20 points
IBM Rational Build Forge is ranked 19th in Build Automation while Jenkins is ranked 2nd in Build Automation with 83 reviews. IBM Rational Build Forge is rated 9.0, while Jenkins is rated 8.0. The top reviewer of IBM Rational Build Forge writes "Great reporting features and very functional". 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". IBM Rational Build Forge is most compared with Bamboo and Digital.ai Release , whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, Tekton and Harness. See our IBM Rational Build Forge 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.