We performed a comparison between CircleCI 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."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."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"It's a stable product."
"The solution offers continuous integration and continuous delivery."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"Distributed execution of build and test jobs."
"Very easy to understand for newcomers."
"This is a great integration tool and very powerful."
"I like the business logs. It's a very useful tool. Client-server communication is also very fast."
"There are a large number of plugins available for integration with third party systems."
"The deployment of traditional Jenkins is easy."
"It is easy to use."
"I like that you can find a wide range of plugins for Jenkins."
"Billing is a mess."
"There needs to be some improvement in the user interface of CircleCI."
"The solution’s pricing could be better."
"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."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"A more user-friendly UI for creating pipelines would be helpful."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"The bug fix speed is very slow."
"The documentation on plugin development could be better: more examples. "
"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."
"I would like to see even more integrations included in the next release."
"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."
CircleCI is ranked 11th in Build Automation with 5 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. CircleCI is rated 6.6, while Jenkins is rated 8.0. The top reviewer of CircleCI writes "Unhelpful support, unclear billing, and has offers ability to track usage". 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". CircleCI is most compared with TeamCity, Tekton, GitHub Actions, AWS CodeBuild and GoCD, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Microsoft Azure. See our CircleCI 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.