We performed a comparison between CircleCI, IBM Rational Build Forge, and Jenkins based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation."Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"The solution offers continuous integration and continuous delivery."
"It's a stable product."
"The ability to automate the build process in a seamless way and run workflows effortlessly. It supports parallel builds so it can scale well. Also, it covers the basics of any build and integration tool, including email notifications (especially when tests are fixed), project insights, etc."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"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."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."
"It is a stable solution."
"Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"The most valuable feature of the solution is its integration between different tools."
"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"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."
"There needs to be some improvement in the user interface of CircleCI."
"Integration with Microsoft Azure is one area for improvement. Azure is growing in its user base, and supports various cloud infrastructure components such as Service Fabric, App Service, etc. Some of Azure’s deployment models (like Kudu) require a steep learning curve, but if CircleCI would come up with such features (deployment to App Service) out of the box, it would be amazing."
"The solution’s pricing could be better."
"Billing is a mess."
"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."
"The enterprise version is less stable than the open-source version."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"Partition security for the workflow of projects is not yet an option."
"Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do."
"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."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"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."
Earn 20 points
