A cloud solution to build automation tool with Incident Management tool integration but is expensive
What is our primary use case?
Our use cases are very generic use cases, such as any kind of integration and pipeline code, the pipeline run, and any kind of information.
We use the solution to send the information to the respective service owner via any channel. So, these are the generic features that everyone is using of CircleCI.
Whatever business needs or requirements we have, CircleCI provides all those types. So, we are also integrating with our incident management tools. Integration is straightforward. For example, CircleCI integration to our GitLab pipeline and hardly takes five to ten minutes.
What needs improvement?
The solution’s pricing could be better.
In future releases, it may provide integration with Grafana or any tool for visualization.
For how long have I used the solution?
I have been using CircleCI for more than eight years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
It is a scalable product.
How are customer service and support?
The documentation provided is quite understandable by the developers and the integration team. So, it's self-sufficient and enables us to understand. So we didn't need to reach out for support.
What about the implementation team?
We deployed the solution in-house. Developers on our site in our organization integrate this for their pipeline by themselves. We do not have any third-party help.
What's my experience with pricing, setup cost, and licensing?
We pay for the license. The product is expensive, but worth the price. The features and integrations of the tools provided are properly utilized. So, it is worth the price.
What other advice do I have?
I recommend the product for end-to-end development for highly scalable, distributed, and microservices, where there are more than 100-200 services integrating together to build a platform.
Overall, I rate the solution a seven out of ten.
CircleCI is one of the best continuous integration and continuous delivery platform
What do you like best about the product?
CircleCI is easy to set up and manage.
You can easily create projects in CircleCI and configure config.yml to define your CI pipeline.
We have set up multiple projects in CircleCI, and CI pipelines are working fine.
CircleCI also gives an option to setup a self-hosted runner where you are not dependent on Circle CI backend infra to run your pipelines.
What do you dislike about the product?
Sometimes CI pipelines may fail if they run on Circle CI infra due to unavailability or high load.
We ran multiple CI/CD pipelines in Circle CI and did not see many issues.
What problems is the product solving and how is that benefiting you?
We have set up multiple projects in CircleCI, and CI pipelines are working fine.
We have also set up self-hosted runners in Circle CI which is helping us to use our own infra to run pipelines.
CircleCI is easy to setup and manage.
My CircleCI Feedback & Recommendation(s)
What do you like best about the product?
Overall, I like the UI and real-time view of the projects along with the commit history.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Quick test runs and immediate feedback.
Several ML services in production use greatly CircleCI
What do you like best about the product?
Easy interface, to see the pregress of the pipelines, using yaml file to create the pipelines easily, so that they run automatically.
What do you dislike about the product?
There was a data breach some time ago. Sometimes the servers are a bit slow.
What problems is the product solving and how is that benefiting you?
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
A good CI/CD tool
What do you like best about the product?
The best thing is the ability to re-start a test step wtih SSH and see what failed, mess around the pod to fix it, and then commit on your local machine.
What do you dislike about the product?
It is expensive. There are various plans, but the cost was too great for us.
What problems is the product solving and how is that benefiting you?
It is a CI/CD tool, that's what it does.
CircleCI Integration: Review and Implementation
What do you like best about the product?
Its seamless integration with popular version control systems like GitHub and Bitbucket. This allows developers to quickly set up and configure continuous integration and delivery pipelines for their projects.CircleCI also provides excellent scalability and performance, allowing for efficient parallel execution of tests and builds. Overall, CircleCI offers a reliable and robust CI/CD solution that dramatically simplifies the process of automating software builds, tests, and deployments.
What do you dislike about the product?
CircleCI primarily focuses on cloud-based CI/CD workflows, which may not align well with specific local development or on-premises deployment scenarios. This can be a limitation for organizations with specific requirements.
What problems is the product solving and how is that benefiting you?
Automation of Build and Test Processes,
Continuous Integration,
Scalability and Parallelism,
Multi-platform and Multi-language Support,
Visibility and Monitoring
Just because it works, doesn't mean there isn't another way to do it
What do you like best about the product?
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.
What do you dislike about the product?
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
What problems is the product solving and how is that benefiting you?
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.
Good product, full functionalities
What do you like best about the product?
Good integration
Easy to use
Nice UI, user friendly
What do you dislike about the product?
The ORB programming is hard to understand
needs more tutorials & documentation
Need good community support for new functionality
What problems is the product solving and how is that benefiting you?
CI as a service
Circle CI as an pre code review check
What do you like best about the product?
We use CircleCI as a pre-check on commits, before doing the actual code review, integrated to phabricator. As our codebase grows, running lint checkers and tests locally before opening a code review takes a long time, so we usually do not do it locally and leave it to the CI, trading our time in running automatic checks for focusing on other tasks. It also help us locate adjusts to our commits before the actual code review, the CI will indicate and error on the commit and not send it to the next step, peer review.
What do you dislike about the product?
I am not in charge of configuration and maintenance of the CI on my company, but sometimes we have problems where the automation stops working, sometimes it would run the tests we delegated to it but not make a post-test change on the commit status (would not change it to ready to review)
What problems is the product solving and how is that benefiting you?
In my company, we use CI in two moments. First, running tests and linter on code reviews, before making it reviewable to peers and once it hits the master branch, to check if everything is ok even after the rebase.
First use guarantee us that we will be reviewing a commit that already had some checks ran on it, that means if that commit broke something else on the code, and it is covered by test, of course, we will be able to notice it and work on adjusts before an actual peer reviews it.
The second use makes sure that, once the commit is approved and then sent to master, the rebase/merge with master branch did not break anything in the project. It is important to us since we have different teams working on different parts of the product, and sometimes they share components, resources or need to adjust something in the whole product.
Go to tool for CI! :)
What do you like best about the product?
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!
What do you dislike about the product?
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 :)
What problems is the product solving and how is that benefiting you?
Application releases, running unit tests on each and every PR and branch as well as testing automated builds.
