External reviews
492 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Good mostly because free for private repositories
What do you like best about the product?
Being free for private repositories, some way to use docker containers
What do you dislike about the product?
UI/UX workflow is very heavy and unintuitive, machines often don't work
What problems is the product solving and how is that benefiting you?
Having a CI which is free for private repositories mostly
Better than hosting and managing your own CI/CD
What do you like best about the product?
I like how it integrates with GitHub and the UI is fairly streamlined. Also, the documentation is decent.
What do you dislike about the product?
Nothing specific, although I remember encountering issues when sorting out the dependency cache.
What problems is the product solving and how is that benefiting you?
Providing continuous integration and automation around all of our codebases in order to ensure quality and consistency.
Recommendations to others considering the product:
I recommend trying out several comparable solutions to make sure the one you select is a good fit. Also, a managed service is preferable to maintaining your own based on experience. You need to have a fairly specific need.
Good. But lagging behind Github Actions
What do you like best about the product?
Good conceptual model for doing CI, good features, good UI. Better CI concepts. It offered simple integration with Github (obviously industry standard), good permission controls, especially across organizations. A relatively good UI and straightforward billing model (discounted when activated from Github).
What do you dislike about the product?
Lack of sharable library and buy in for said feature from community. Seems "heavy". Multiple workflows would be really nice.
What problems is the product solving and how is that benefiting you?
Continuous Integration and Continuous Deployment, automated deployment, builds, artifact generation and continuous testing. We maintain a mono repo and so getting builds right is important. Circle CI's caching mechanisms were especially useful there, but slightly too slow to be fully used. We ended up switching to an inhouse S3 based solution. Faster docker image downloads and better layer caching would also be particularly useful. Until Circle CI gets better at offering a lightweight experience, with multiple flows and better modularity and sharability, ill be using github. Very tight integration with Github will make the effort to use a separate platform over githubs internal options are really required.
Recommendations to others considering the product:
Use Circle CI for a solid CI/CD experience, but consider Github Actions for a more lightweight, extensible experience.
It Integrates, It Deploys, ad it does so continuously!
What do you like best about the product?
Integration with github works pretty well. I like that I can click in Github and then it wil lautomatically bring me to Circler CI and there I can see what the error is although sometimes it is hard to scroll to find the error I am looking for. I have no strong feelins on the old vs the new interface, they are both alright if you ask me
What do you dislike about the product?
some menu options are confusing, especially when deploying and trying to find it under workflow vs. jobs. I often have to search for where something I just deployed it running, and once or twice thought it did not run when it did because I was looking in the wrong place. Also apparently theres a dicfference if I click on the repo name vs click on the master branch name in the dropdown and i dont really get why
What problems is the product solving and how is that benefiting you?
Great for finding errors that crop up
Recommendations to others considering the product:
I don't have any strong feelings one way or the other. It gets the job done I guess. That's mostly all I ask for.
Still scratching the surface of what Circle CI can do
What do you like best about the product?
Easy to use and high level support team.
What do you dislike about the product?
Pricing plan in terms of credit is not always the best.
What problems is the product solving and how is that benefiting you?
Decreased build time.
Easy CI setup
What do you like best about the product?
Automatically deploy depending on which branch is pushed to; easy integration with Github to ensure tests pass before merge
What do you dislike about the product?
Finding some settings in the UI can be difficult
What problems is the product solving and how is that benefiting you?
Requiring QA and unit tests to pass prior to merge to prevent regressions; not having to deploy anything manually
CircleCI is very good tool but there're some problem with on-premises
What do you like best about the product?
I can write the configuration for CircleCI very easily.
And I can login to the build job container using SSH, this is a big advantage than Jenkins.
I also manages Jenkins cluster. With Jenkins, users want us to install plugins they want to use.
CircleCI uses containers to build each jobs so users can install any dependencies of their application even if it is a system components like glibc.
Also, other users using CircleCI can login to their job.
This means the user can do trouble shooting by their selves. This is a big advantage than Jenkins, too.
And I can login to the build job container using SSH, this is a big advantage than Jenkins.
I also manages Jenkins cluster. With Jenkins, users want us to install plugins they want to use.
CircleCI uses containers to build each jobs so users can install any dependencies of their application even if it is a system components like glibc.
Also, other users using CircleCI can login to their job.
This means the user can do trouble shooting by their selves. This is a big advantage than Jenkins, too.
What do you dislike about the product?
We're using CircleCI enterprise on our on-premise servers, not AWS.
With this environment, we cannot use docker on CircleCI Jobs.
This means we cannot build Docker images on CircleCI, need to prepare other docker host to build them...
With this reason, I cannot recommend to use CircleCI to my colleagues in my company.
All features except docker related issues are very good so this is very, very disappointment thing...
With this environment, we cannot use docker on CircleCI Jobs.
This means we cannot build Docker images on CircleCI, need to prepare other docker host to build them...
With this reason, I cannot recommend to use CircleCI to my colleagues in my company.
All features except docker related issues are very good so this is very, very disappointment thing...
What problems is the product solving and how is that benefiting you?
I'm testing and building my application on CircleCI.
I can test my application with very easy YAML formatted configuration file.
The jobs are run in containers, separated environment. so there's no problems related with other jobs.
I also release my application if the git branch is master.
We can use manual approval in the CircleCI workflow, it makes us being able to use CircleCI for Continuous-Deployment with production release.
I can test my application with very easy YAML formatted configuration file.
The jobs are run in containers, separated environment. so there's no problems related with other jobs.
I also release my application if the git branch is master.
We can use manual approval in the CircleCI workflow, it makes us being able to use CircleCI for Continuous-Deployment with production release.
Recommendations to others considering the product:
CircleCI is very good tool to do Continuous-Integration or Continuous-Delivery if you can use circleci.com or run CircleCI Enterprise on AWS.
If you want to run your on on-premise servers, it causes some painful situation.
If you want to run your on on-premise servers, it causes some painful situation.
CI for everyone
What do you like best about the product?
I had a good experience with Circle CI/CD platform and would recommend it to everyone.
What do you dislike about the product?
It was a company account and when the person who set it up left all jobs came to stop.
What problems is the product solving and how is that benefiting you?
Every commit is potentially a release candidate. CircleCI streamlines the process of deployment.
Recommendations to others considering the product:
Consider your commits as release candidates and CI/CD as automatic way to deliver those candidates into production environment. CI/CD tools greatly help to minimize Lead Time KPI.
We used CircleCI last few years. But now we considering move to github action.
What do you like best about the product?
I think CircleCI most powerful feature is macOS hosting. I was use to Jenkins. But it needs macOS server to using iOS. We are using AWS but unfortunately AWS doesn't support macOS. So CircleCI was good alternative.
What do you dislike about the product?
Sometimes It is hard to find out build error on CircleCI. I had a few experiences that fail build. So we are considering move to Github actions.
What problems is the product solving and how is that benefiting you?
CircleCI was almost all solution about CI including macOS support. Specially I liked simple usage through yml.
Automation helps our team deliver fast
What do you like best about the product?
E2e test with screenshots is very helping, Easy integration with AWS.
What do you dislike about the product?
Takes a long time to build and test large application
What problems is the product solving and how is that benefiting you?
Gated check-in
showing 11 - 20