CircleCI Reviews

Very user friendly interface & features, such as flaky test detection or insights for workflows/job/branches that are not seen so often in other CI providers.

Audit features are not as available as other enterprise-grade CI providers.

It's solving the need to provision our own CI servers, and that the various build host support e.g. Mac runners is definitely a standing out point.

The free tier of CircleCI includes 30,000 which is usually enough for small projects. It is pretty easy to use it once u get the hang of including CircleCI in your projects. You can even SSH into the build so that if any issue arises you can solve it directly in the machine, instead of trying to figure out where the issue is locally.

The initial setup for CircleCI can be a bit more complex when compared to other tools like Github actions, but it's nothing that a bit of introspection cannot solve. Also when using Docker layer caching the credits run out too fast. There should be a warning for the same , since I did not realize that caching would use so many credits.

I was able to integrate CircleCI successfully into one of our projects on Github, so we dont have to worry anymore about breaking changes being pushed into the repo. You can SSH into the build so that if any issue arises you can solve it directly in the machine, instead of trying to figure out where the issue is locally.

Overall, I like the UI and real-time view of the projects along with the commit history.

CircleCI has not updated its dependencies in some time. When I run Cypress v.12, it passes locally but fails in the pipeline due to how the extensions are handled.

Quick test runs and immediate feedback.

Easy interface, to see the pregress of the pipelines, using yaml file to create the pipelines easily, so that they run automatically.

There was a data breach some time ago. Sometimes the servers are a bit slow.

ML data products, to train models and to deliver them in production; but also other automatic scripts, as well as R&D data science repos

It is really simple to use, integrate with other technologies, and has great documentation to follow.

Someone coming from the DevOps/Sysadmin role, with a little knowledge can easily connect the dots on what CircleCI offers.

The docker layer cache and IP ranges seem to be a bit too expensive for usage. I'm not saying it doesn't work actually, it does, but the price is kinda expensive

We used to have an old implementation with other technology(Jenkins). It worked fine. The issue is that the process was a little slow, and not totally integrated with the repository.

Love almost everything about CircleCI :) Is very robust as a CI tool, and I love the fact that everything is documented really well. Orbs implementations are very useful and just perfect!

Nothing much to comment on about CircleCI. I'm not aware if its possible to have a GitHub integration to view the pipelines via GitHub itself but it would be a nice to have :)

Application releases, running unit tests on each and every PR and branch as well as testing automated builds.

It's really convenient to test our codes automatically online. It will not block what I'm doing so I can push my work forward offline while CI running online.

It's unstable sometimes. Sometimes it will give us a wrong result. And sometimes it took way too much time to finish all the tests.

Running tests.

Checking code styles.

Checking resources availability.

The easy that is to use orbs and previous work from other teams and companies that had made it public.

Also I can connect multiple repos very fast and without any problems

As with any other CI/CD tool, the complexity of testing things during the development or improvement of the pipelines that we have. Is impossible to recreate it

Previously we were using another tool that took us about 2 hours the build of our products. Now we build more than ten apps simultaneously in about 30 minutes. It has made a difference

Their UI is great. Setting up the CI pipeline, with all the docker features and different options makes it a great option to have in you CI pipeline. We use it in all of our repositories and help us run all of our test with each commit and PR

There's really nothing that comes to mind as something negative about CircleCI. Sometimes the CI setup requires some updating (some old versions stop beign supported, etc), but CircleCI makes it super easy

CircleCi helps us to run all or our tests before deploying to production. When the test suite fails it makes it super easy to see the "artifacts" of the test run, screenshots, logs, etc, that help a lot to figure out what happened

It's easy to get started, almost no effort to start

Can't have total control over the machines

Is the best cost bennefict

We have a proper deploy pipeline that has many stages, all detailed in .yml files