CircleCI is used primarily as the pipeline for application deployment. When a pull request is created in GitHub, it triggers a CircleCI pipeline because of the GitHub integration. During the CircleCI pipeline, the application goes through building and deployment to the appropriate destination, which can be a Lambda or AKS microservices.
External reviews
489 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Automated deployments have streamlined cloud releases but configuration orbs still need simplification
What is our primary use case?
What is most valuable?
CircleCI's GitHub integration is the best feature offered. The GitHub integration is most valuable because of its ease of use, as it only requires integration with the GitHub repository and then creating the pipeline as a YAML file within the repository code.
CircleCI has positively impacted the organization, as it has been used for many years and serves as the main source for application deployment. Every deployment is conducted through CircleCI, and this is what keeps the company functioning.
What needs improvement?
CircleCI's Orbs are not as easy to use as they could be. If CircleCI implemented a function approach similar to GitHub Actions, it would be significantly better.
CircleCI could be improved if it could function without Orbs. Instead of Orbs, using a function approach like GitHub Actions would be beneficial.
For how long have I used the solution?
CircleCI has been used for two years.
What do I think about the stability of the solution?
CircleCI is stable.
What do I think about the scalability of the solution?
CircleCI's scalability is easier to manage, but it comes at a high cost.
How are customer service and support?
A customer support ticket has never been opened.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
This company already had CircleCI running for several years before starting at this position.
How was the initial setup?
CircleCI was purchased through the AWS Marketplace.
What about the implementation team?
The company does not have a business relationship with this vendor beyond being a customer.
What was our ROI?
A return on investment with CircleCI has not been observed, and no relevant metrics such as time saved or fewer employees needed can be shared.
What's my experience with pricing, setup cost, and licensing?
There is not much experience with pricing, setup cost, and licensing because that is managed by the legal team.
Which other solutions did I evaluate?
Other options were not evaluated before choosing CircleCI, but after choosing CircleCI, GitHub Actions and Harness are already being evaluated.
What other advice do I have?
For others looking into using CircleCI, study thoroughly about CircleCI's Orbs because they are quite complicated. The overall review rating for CircleCI is 6 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Very very good tool easy to login from github
What do you like best about the product?
Very very good tool easy to login from github
What do you dislike about the product?
Nothing as of now. Looking forward for more
What problems is the product solving and how is that benefiting you?
Very very good tool easy to login from github. But as of now no problem
CircleCI with GitHub offers powerful CI/CD automation with excellent Git integration
What do you like best about the product?
CircleCI integrates seamlessly with GitHub, making it easy to trigger builds on commits and pull requests. It offers a highly configurable pipeline setup using YAML, supports Docker natively, and allows for parallel job execution to speed up testing. The free tier is generous enough for small to mid-size projects, and built-in caching and performance dashboards help optimize build times and monitor efficiency.
What do you dislike about the product?
However, the learning curve can be steep for those new to CI/CD or YAML configuration. Resource limits in the free plan can be restrictive for larger teams or complex workflows. Job startup times can occasionally be slow, the UI sometimes lags under load, and advanced features like Docker layer caching are locked behind paid tiers.
What problems is the product solving and how is that benefiting you?
Automatically triggers builds on every push or pull request.
Solid Tool for easy CI
What do you like best about the product?
Integrations are great. Configuration was easy and has a solid number of features. We use this in our CI for a handful of apps and it's very easy to use.
What do you dislike about the product?
Wish it had better integrations for mobile apps (android / iOS) alternatives have easy integrations into those developer platforms to pull certificates etc.
What problems is the product solving and how is that benefiting you?
Not running deploys locally. Centralization of environment variables
my experience using CircleCI is the best
What do you like best about the product?
what i like the best about CicleCI is its speed and flexibility, and automation of testing and user friendly interface. and easy to implement and its easy to approach the customer support
What do you dislike about the product?
i think one of the downsideof circleCI is the complex of configuration for newbie or begginners, especially with advance feature
What problems is the product solving and how is that benefiting you?
one of the problem that circleCI solve is manual, thanks to CircleCI we now automate on testing our software and automate fo find error, so now we can fix it early, its reduce our time on working, and improve the team productivity
It is a great platform to coordinate your CI/CD
What do you like best about the product?
It is really easy to integrate with GitHub and Gitlab. On the other hand I really like that my team can easily take advantage of the platform to understand the problems that may occur with the pipelines, is really easy to identify the problem by checking logs and identify the step that is failing.
What do you dislike about the product?
The pricing page is a little bit confusing for me. But maybe this is just me because I'm not using this section very regularly, however when i enter I always forgot how to do the report I need and the UI is not very intuitive
What problems is the product solving and how is that benefiting you?
We have the CI/CD pipelines inside CircleCI for the 2 main products in the company. A mobile application and the backend API that is used by all the clients inside our system. The benefit of having the pipelines here is that engineers can easily understand problems with deployments without the help from the DevOps team. They can easily understand the issues and fixing by themselves most of the cases
A review of CircleCi
What do you like best about the product?
The Continious integration server is operating mainly online through Single sign on to Github or E-mail authentication. I shall confess that the integration server is fast. It was built to speed up releases. Besides, all those features, their cloud plans enpower their solution.
What do you dislike about the product?
I hope their customer support team will focus on customer success and satisfaction to include the customer feedback in their upcoming horizons.
What problems is the product solving and how is that benefiting you?
CircleCi sorts out the speed matter. It is faster than other solutions and was developed to get rid off this problem.
Besides, the solution is innovative. From ideas, reach concrete solutions and make them better through automation.
Also, It is a viable solution which is user friendly through the configuration of yaml files.
Besides, the solution is innovative. From ideas, reach concrete solutions and make them better through automation.
Also, It is a viable solution which is user friendly through the configuration of yaml files.
Unhelpful support, unclear billing, and has offers ability to track usage
What is our primary use case?
What is most valuable?
The solution offers continuous integration and continuous delivery.
What needs improvement?
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 and understand issues when emailing them. They reply to me with a totally different context about the problem. Just yesterday, my web applications failed to 'yarn build' after I downgraded the resource class from extr-large to large. I contacted support and got no reply.
Billing is a mess. There is duplicate information in the bill downloaded from their website and when I asked for a consolidated bill, they just answered that they didn't have it.
There is no transparency on how many billed minutes and credits I spent each day both on their website and the monthly bill which makes it difficult to understand when the monthly bill contains many refill item charges.
It is difficult or impossible to track usage and burndown of my subscription and to gain total outstanding refill amounts on a daily basis. Their website doesn't provide sufficient information on credits allocated/calculated for my extra-large resource class.
For how long have I used the solution?
I've used the solution for five years.
How are customer service and support?
Support is no good! They are low-skilled and there is a long response time.
How would you rate customer service and support?
Negative
What's my experience with pricing, setup cost, and licensing?
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 details on how your subscription burn downs and how much is carried forward to the next billing cycle.
Terrible support and rubbish billing!
What do you like best about the product?
Ease of use, ease of implementation, nothing else!
What do you dislike about the product?
Occasional connectivity issues, nonsense 137 OOM and infrastructure failure which result in build failures with no part on our end. That costs us credits. 137 OOM error happens from time to time to our Node.JS application when their dashboard resources show that RAM consumption is only 50%. Support engineers do not thoroughly read and understand issues when email them at support@circleci.com and reply me with totally different context about the problem. Just yesterday, my web applications fail to `yarn build` after I downgrade the resource class from xlarge to large. Contacted support but no reply.
Billing is a fucking mess and nightmare! There are duplicate information in the bill downloaded from their website and when I asked for consolidated bill, they just answer don't have it. There is no transparency on how many build minutes and credits I spent each day both on their website and the monthly bill which make it difficult to understand when the monthly bill contains many refill item charges. It is difficult or impossible to track usage and burndown of my subscription and total outstanding refill amounts on a daily basis. For example, I went through the build history for the 3 days into the new billing cycle. There were a total of 74 build and when I sum up the duration of the build, it is 597m 41s. However, their fucking rubbish dashboard shows 4265 "Compute" minutes. Is this a SCAM?
Billing is a fucking mess and nightmare! There are duplicate information in the bill downloaded from their website and when I asked for consolidated bill, they just answer don't have it. There is no transparency on how many build minutes and credits I spent each day both on their website and the monthly bill which make it difficult to understand when the monthly bill contains many refill item charges. It is difficult or impossible to track usage and burndown of my subscription and total outstanding refill amounts on a daily basis. For example, I went through the build history for the 3 days into the new billing cycle. There were a total of 74 build and when I sum up the duration of the build, it is 597m 41s. However, their fucking rubbish dashboard shows 4265 "Compute" minutes. Is this a SCAM?
What problems is the product solving and how is that benefiting you?
CI/CD
A really cool tool for your CI/CD operations.
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
showing 1 - 10