CircleCI Reviews and Ratings

Use Cases and Deployment Scope

We use CircleCI as our centralised Continuous Delivery engine for our platform. It orchestrates the entire application lifecycle, from code commit to deployment, across our distinct environments and two major platforms (Web and Mobile). It addresses the following Business Problems: 1. CircleCI eliminates our Environment Inconsistency, by automated builds in isolated Docker environments that ensure code behaves identically in production as it does during our development. 2. CircleCI accelerates our Mobile releases by automating the complex build-and-sign process for iOS and Android with Fastlane, and we significantly reduce manual effort and time-to-market for mobile updates. 3. CircleCI enhances our security & compliance by integrating Snyk scans automatically, which allows us to detect vulnerabilities in dependencies and containers before deployment, ensuring every release meets security standards. 4. CircleCI helps us in mitigating our Production risks by implementing manual approval gates, which prevent accidental deployments, giving our team control and confidence in update rollouts.

Likelihood to Recommend

Based on our experience, CircleCI is well-suited for automating mobile app release cycles. For example, to release an iOS app, you would need to build, sign, and upload it to TestFlight, which requires a dedicated Mac in the office. But with CircleCI, you can have macOS executors, so you don't have to manage a physical build machine. Another benefit is that CircleCI's certified AWS Orbs abstract away complex authentication and deployment logic, allowing us to build, push, and deploy Docker containers to Amazon ECS with minimal configuration and high reliability. CircleCI is less suited for smaller projects where the development and deployment are not that extensive, for example, a static site. Once you have built a static site, you probably won't make any further changes, so there's no point in paying for it.

Use Cases and Deployment Scope

We use CircleCI for continuous integration and delivery of our mobile app. The main users are our DevOps team to help manage code releases. It's helped us push code to production with a standardize process and can now ensure we get a build with each merge. Our codebase is ReactNative and run on AWS CloudFront.

Likelihood to Recommend

It's one of the stronger options when we considered CI/CD solutions. It's commonly used in the industry so when we have new team members join it's easy for them to pick up. Generally it's been reliable aside from a few outages. I would recommend this for any software teams that also run automated tests.

Use Cases and Deployment Scope

We use CircleCI to deploy our app to various environments as well as run integration and E2E tests. This allows these processes to run independently from an individual machine.

Likelihood to Recommend

CircleCI is perfect for our needs. It allows us to merge a release branch into an environment branch and the deploy workflow kicks off automatically. It further allows us to add integration testing and E2E testing right into the build workflow.

Use Cases and Deployment Scope

We use CircleCI as an independent part of our continuous integration testing process, which handles both automated building and testing our software projects, as well as with our deployment pipelines to power constant delivery efforts. We use CircleCI because their environment is exceptionally customizable and generally reliable for our needs. There is also a generous free tier.

Likelihood to Recommend

CircleCI has been an excellent option for us for several years. Still, we're beginning to invest in Github Actions and other platforms where CricleCI runs closer to our existing test and deployment pipelines. Because so many different integrations exist, it's easily adaptable to many kinds of applications. At this point, though, it's worth looking at the CircleCI embedded in other parts of the deployment pipeline before concluding that CircleCI is the best direction to go in.

Use Cases and Deployment Scope

We use CircleCI for most of our development workflows. Building, testing and deploying. We use it across most teams and departments.

It integrated nicely with GitHub and we are able to validate every change on every branch before merging and automatically deploying to production. I use it for both Ruby and React projects.

Likelihood to Recommend

We have many developers that push to production every day. Every branch runs continuous integration on CircleCI and clearly links to GitHub with an indication on whether it failed or passed.

Things work fine when you work against the GitHub links but searching on the CircleCI site is not intuitive.

Configuration with YAML files can also be hard to do and some UI tools for scaffolding them would be nice.

Use Cases and Deployment Scope

At the moment, Circle is used across the company to make continuous integration and continuous delivery for the mobile native applications. Circle went to solve us the problem of have a dynamic and easy-to-use cloud-based continuous integration and delivery for mobile, without the maintenance cost of the resources and using only for the computing use.

Likelihood to Recommend

Circle suits if you're looking for a cloud-based continuous integration and continuous delivery system for web and native-based applications. The uptime is very good and the features included in the platform are very useful.

On the other hand, it's a little difficult to combine Circle with your on-premise stuff, such as registry dependencies (npm, Maven Nexus, etc) ... because the only way is to give Circle access to your on-premise network and it could be a little insecure.

Use Cases and Deployment Scope

CircleCI is being used as the main product for continuous integration, continuous delivery software development. It's being used primarily by release management/engineering and software engineering teams. It is solving the problem of needing to build a process around pushing code into production and following a schedule where code is continually deployed.

Likelihood to Recommend

CircleCI is one of the best CI/CD pipeline tools available. I'm not sure I can advise anything else besides this because it's still the most used and continually developed tools.

Use Cases and Deployment Scope

We've used CircleCI for the automation of build and test for smaller scale projects, in combination with another set of tools for continual deployment, hosting and visual testing. CircleCI is a great interface for viewing and managing automated jobs and workflows, and has made the process of CI more accessible for the team as a whole.

Likelihood to Recommend

Great for quick setup of new projects, but may not be the most suitable to large scale production apps (not from experience, but the level of detail may not be sufficient - at least on the free tier).

Use Cases and Deployment Scope

CircleCI is being used by my team as a continuous integration / continuous deployment pipeline for code and various other programmatic work. The business problems it addresses is the deployment, testing, and productionization of code supporting our main software engineering functions. Various other teams we work with also go along this pathway and use circle or other tools.

Likelihood to Recommend

CircleCI is great when you have software engineering processes that you need to take out and drastically scale and test before deployment. It works with regular code structures where there's a procedural lifecycle and where there is a need to methodically test and deploy code in an automated manner so deployments no longer need to be done by hand.

Use Cases and Deployment Scope

We use CircleCI to run our React tests as well as build and deploy our React code to AWS CloudFront on both staging and production.

Likelihood to Recommend

CircleCI is well suited for a small team that needs to run tests on web app codes like Ruby on Rails, React, Python, etc. It's not as well suited for larger teams as the cost quickly scales up. It's also not well suited for more complicated builds because the configuration process is pretty arcane.