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 automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"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."
"It's a stable product."
"The solution offers continuous integration and continuous delivery."
"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"It can scale easily."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"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."
"It is easy to use."
"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."
"Billing is a mess."
"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."
"There needs to be some improvement in the user interface of CircleCI."
"The solution’s pricing could be better."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"The learning curve is quite steep at the moment."
"Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."
"Logging could be improved to offer a clearer view."
"The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"The user interface could be updated a little."
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.
