CircleCI - MCP Server
CircleCIExternal reviews
498 reviews
from
and
External reviews are not included in the AWS star rating for the product.
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
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
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.
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.
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.
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.
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.
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
Continuous Integration,
Scalability and Parallelism,
Multi-platform and Multi-language Support,
Visibility and Monitoring
Good product, full functionalities
What do you like best about the product?
Good integration
Easy to use
Nice UI, user friendly
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
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.
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.
Good experience, faced multiple outages that affected our releases couple of times.
What do you like best about the product?
ssh to the container
re-run from failed
re-run from start
nice UI
re-run from failed
re-run from start
nice UI
What do you dislike about the product?
downtine in 2 cruciel releases (bad luck)
pipeline fails for a strange error and succeeds after re-run which is kind of weird
sometimes the pipeline finishes but the status still shows running unless i refresh the page
our keys were exposed after a security breach!!
pipeline fails for a strange error and succeeds after re-run which is kind of weird
sometimes the pipeline finishes but the status still shows running unless i refresh the page
our keys were exposed after a security breach!!
What problems is the product solving and how is that benefiting you?
making sure that no one pushes a code that doesn't pass our linting standards, integration tests, unit tests, functional tests ....
creating the docker image
creating the docker image
showing 11 - 20