Likelihood to Recommend It is really good for building projects in the cloud. If you try to do build the project first locally and then push that stack to the cloud it could take a lot of time. In this way, it also consumes a lot of resources in the computer and in the network.
Read full review CircleCI is perfect for a CI/CD pipeline for an app using a standard build process. It'll take more work for a complex build process, but should still be up to the task unless you need a lot of integrations with other tools. If you have a big team and can spare someone to focus full time on just the CI/CD tools, maybe something like Jenkins is better, but if you're just looking to get your app built, tested, and delivered without a huge amount of effort, CircleCI is probably your preferred tool.
Read full review Pros Customization Do code builds within a schedule or when the source code changes Only pay for the build time used Read full review Multiple builds can be run at the same time in parallel. The CircleCI web interface (UI/UX) is very easy to understand and use. Easy Configuration to learn and use. Just a single configuration YAML file. Many integrations. We use the GItHub, Slack, and DataDog integrations. Read full review Cons Sometimes it runs an outage and developers don't know why. We have to contact DevOps most of the time. Sometimes it is slow Read full review The "phases" their config file uses to separate out options seem very arbitrary and are not very helpful for organizing your config file No way that I know of to configure which version of MongoDB you use. You have to write your own shell script to download and start MongoDB if you want a specific version. Hard to access build artifacts in the UI Read full review Usability CircleCI interface is awesome in that it is relatively modern and makes it clear exactly which parts of the engineering lifecycle you are in
Read full review Performance It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
Read full review Support Rating Unless you have a reasonably large account, you're going to be mainly stuck reading their documentation. Which has improved somewhat over the years but is still extremely limited compared to a platform like Digital Ocean who invested in the documentation and a community to ensure it's kept up to date. If you can't find your answer there, you can be stuck.
Read full review Alternatives Considered AWS CodeBuild provides the option to fully implement the build in the cloud without wasting your local resources (computer and network) providing independence to developers to invest those resources in other processes. It also provides a robust platform with a lot of customizations or just a script for each language.
Read full review Circle was the first CI with simple setup, great documentation, and tight integration with
GitHub . Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when we switched.
Read full review Return on Investment Read full review It has eased the burden of standardizing our testing and deployment, making onboarding new developers much faster, and having to fix deployment mistakes much less often. It allows us to focus our process around the GitHub workflow, ignoring the details of whatever environment the thing we're working on is actually hosted in. This saves us time. Read full review ScreenShots