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."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 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."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."
"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."
"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 are Jenkins Pipelines for ALM and full Deploy Cycle."
"The most valuable feature is its ability to connect with different tools and technologies."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"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."
"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."
"Billing is a mess."
"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 UI must be more user-friendly."
"There is no way for the cloud repositories to trigger Jenkins."
"It could be cheaper."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."
"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."
"The documentation is not helpful, as it is not user-friendly."
"The support for the latest Java Runtime Environment should be improved."
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 Concourse for VMware Tanzu. 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.