CircleCI - MCP Server
CircleCIExternal reviews
490 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Fast and easy way to add CI to your project
What do you like best about the product?
Really easy to get started. The integration with Github worked well -- most everything just seemed to work right away. The documentation is much better than most tools out there and the sales/product engineers have been great to talk to as we were ramping up our integration.
What do you dislike about the product?
There isn't an easy way to manually trigger a job apart from opening a pull request. Not having dynamic workflows means you need to do a bunch of conditional logic in bash to skip parts of your workflow that depend on state.
What problems is the product solving and how is that benefiting you?
Standard CI in which we run tests when a new pull request is opened. When the developer merges to master, we build and deploy to AWS. We've seen similar costs to running our own Jenkins instance but have experienced far fewer operational issues with CircleCI. Its UI is easy to use so non-DevOps people can use it without assistance.
Good, but becoming great!
What do you like best about the product?
CircleCI easily integrates with third-party tools and services.
What do you dislike about the product?
The complexity of workflow management can difficult to tackle as you begin to use CircleCI.
What problems is the product solving and how is that benefiting you?
Pull-request reviews workflows has been our key use-case with CircleCI.
Recommendations to others considering the product:
Give it a shot. It has a great trial plan, and you'll quickly see the benefits.
Positive experience
What do you like best about the product?
I love how useful and specific CircleCI is in showing which commits are broken.
What do you dislike about the product?
Can be slow to run, which it had a faster build time.
What problems is the product solving and how is that benefiting you?
We are ensuring the each of our builds that we release are safe to be deployed.
circleci: easily get strted with CI
What do you like best about the product?
C-CI is very easy to setup and use. A lot less overhand then jenkins and co
What do you dislike about the product?
I dislike that there doesnt seem to be a lot of plugins
What problems is the product solving and how is that benefiting you?
We have standardize all code across our organization and have standardized code quality requirements
Recommendations to others considering the product:
If you want to have a very quick setup with clear docs and very little overhang
Efficient Continuous integration
What do you like best about the product?
Working with CircleCi makes it incredibly easy for me to deploy my code even though I am a new developer.
What do you dislike about the product?
The only thing I don't like about Circle is when it is difficult to navigate a lot of projects since my company has so many different projects.
What problems is the product solving and how is that benefiting you?
Circle Ci allows me to deploy things easily and overwrite changes with a series of a la carte scripts.
Solid CI Pipelines & Infrastructure
What do you like best about the product?
Solid tooling, fast jobs, and good pricing make this a no-brainer. It's quite flexible in its execution environments and docker integration make's it a snap.
What do you dislike about the product?
Earlier this year CircleCI had some significant downtime but they've gotten a lot better. GPU support is coming but limited. Docker vs. Machine builds are important but often the differences are unclear.
What problems is the product solving and how is that benefiting you?
We CircleCI to automate our build pipeline and make CI/CD a snap!
Good continuous deployment monitor/tool
What do you like best about the product?
I like the layout, UI, color scheme, and general look of the application
What do you dislike about the product?
Builds not updating live (from running to success)
What problems is the product solving and how is that benefiting you?
Like the link with Github, very useful
CI made easy
What do you like best about the product?
How easy it is to include CircleCI on a project
What do you dislike about the product?
That CircleCI lives outside our cloud infrastructure
What problems is the product solving and how is that benefiting you?
It would be great if we could run an internal version of CircleCI to access private services, but the benefit of easy and uninvolved testing and deployment scripts via CircleCI has been great
Great CI to use with your applications
What do you like best about the product?
It is easy to understand and helps you with your CI/CD. It performs well, as expected. One of the best I have ever used.
What do you dislike about the product?
Not much to dislike. It has no mayor flaws. The only thing is that sometimes it takes too long to run the jobs, and if you have a set of micro services being deployed at the same time, it will create a queue that can take long to process.
What problems is the product solving and how is that benefiting you?
The main problem that I solve with CircleCI is the CI/CD for my applications. It helps me work with automated deployments and integrations, and keep all the projects coordinated with my teammates.
Recommendations to others considering the product:
It is great, but keep in mind to pay for a better plan if you have a set of micro services.
Works fine for small teams
What do you like best about the product?
It's easy to setup, it supports on project configuration by yaml config file. It is possible to use a range of tools for the complete CI workflow, from source checkout, maven project build, test and deploy to different stages. Its more than enough for projects written on languages that are not memory hunger like Java. They give you 4GB of memory to build your project.
What do you dislike about the product?
Sometimes it takes too long to build, and some features are only available if you pay much more for it. The basic profile is only capable to attend small teams. If you have more people working on the project, doing a lot of commits, you may need to pay much more for it to work.
We have faced a lot of out of service problems on the last couple of months, down times that were critical to the project.
It's very difficult to build an Android project, as it requires a lot of memory to build, specially because the Gradle builder is memory hunger.
We have faced a lot of out of service problems on the last couple of months, down times that were critical to the project.
It's very difficult to build an Android project, as it requires a lot of memory to build, specially because the Gradle builder is memory hunger.
What problems is the product solving and how is that benefiting you?
Implementing the continuous delivery workflow. From build to test and deploy phases.
Recommendations to others considering the product:
Use it when you have a small team, or if it fits your budget, buy the higher profile. But make sure you have tested it with multiple users in one project and check the down times and time it takes to build and run all the required steps in your pipeline before buying the full version of the service.
showing 151 - 160