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."
"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."
"For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"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."
"Jenkins has built good plugins and has a good security platform."
"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."
"Has enabled full automation of the company."
"Having builds and test tasks triggered on commit helps not to break the product."
"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."
"The solution’s pricing could be better."
"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."
"Billing is a mess."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
"We cannot change the ownership of any directory or file or any kind of directory."
"The scriptwriting process could be improved in this solution in the future."
"The upgrades need improvement."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"UI is quite outdated."
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.