CircleCI vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
CircleCI Logo
1,878 views|1,711 comparisons
66% willing to recommend
Jenkins Logo
6,896 views|5,921 comparisons
88% willing to recommend
Comparison Buyer's Guide
Executive Summary

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.
To learn more, read our detailed CircleCI vs. Jenkins Report (Updated: March 2024).
768,415 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"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 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."

More CircleCI Pros →

"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc.""It is very useful for us to be able to collect and manage automatic processing pipelines.""Very easy to understand for newcomers.""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.""When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams.""The solution is scalable and concurrent users have access to the platform.""It can scale easily.""Having builds and test tasks triggered on commit helps not to break the product."

More Jenkins Pros →

Cons
"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.""Billing is a mess.""There needs to be some improvement in the user interface of CircleCI."

More CircleCI Cons →

"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information.""It could be cheaper.""Jenkins could improve the integration with other platforms.""Better and easy-to-use integration with Docker would be an improvement.""It would be helpful if they had a bit more interactive UI.""Support should be provided at no cost, as there is no free support available for any of the free versions.""They need to improve their documentation.""The enterprise version is less stable than the open-source version."

More Jenkins Cons →

Pricing and Cost Advice
  • "The price of CircleCI could be less expensive."
  • More CircleCI Pricing and Cost Advice →

  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    768,415 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:The solution offers continuous integration and continuous delivery.
    Top Answer:Beware of skyrocketing bills as CircleCI does not provide transparency into how they charge refills. Their monthly billing statement is almost unreadable and their online dashboard doesn't provide… more »
    Top Answer:We've had occasional connectivity issues with cloud resources and build failure due to its own internal system setup and environment. That costs us credits. Support engineers do not thoroughly read… more »
    Top Answer:When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ranking
    11th
    out of 41 in Build Automation
    Views
    1,878
    Comparisons
    1,711
    Reviews
    2
    Average Words per Review
    342
    Rating
    4.0
    2nd
    out of 41 in Build Automation
    Views
    6,896
    Comparisons
    5,921
    Reviews
    39
    Average Words per Review
    386
    Rating
    7.8
    Comparisons
    TeamCity logo
    Compared 32% of the time.
    Tekton logo
    Compared 21% of the time.
    GitHub Actions logo
    Compared 8% of the time.
    AWS CodeBuild logo
    Compared 6% of the time.
    GoCD logo
    Compared 4% of the time.
    GitLab logo
    Compared 16% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 9% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Learn More
    Overview
    CircleCI's continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. CircleCI offers a modern software development platform that lets teams ramp quickly, scale easily, and build confidently every day.

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    Sample Customers
    Shopify, Zenefits, Concur Technologies, CyberAgent
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    VISITORS READING REVIEWS
    Computer Software Company18%
    Financial Services Firm12%
    Comms Service Provider7%
    Manufacturing Company7%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    VISITORS READING REVIEWS
    Small Business26%
    Midsize Enterprise13%
    Large Enterprise60%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    CircleCI vs. Jenkins
    March 2024
    Find out what your peers are saying about CircleCI vs. Jenkins and other solutions. Updated: March 2024.
    768,415 professionals have used our research since 2012.

    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.