CircleCI - MCP Server
CircleCIExternal reviews
490 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Great Experience
What do you like best about the product?
Integration with other tools like bitbucket and github
What do you dislike about the product?
Speed of build and running scripts. It makes multiple users queue and build time increases exponentially
What problems is the product solving and how is that benefiting you?
Faster and cleaner deployments that do not break production build
The best of its kind, and constantly improving.
What do you like best about the product?
- Flexible docker-based architecture
- Flexible configurationi, allowing powerful composition with circle orbs, executors, commands and jobs
- Intuitive and fast UI
- Local CLI for replicating workflows locally
- Flexible configurationi, allowing powerful composition with circle orbs, executors, commands and jobs
- Intuitive and fast UI
- Local CLI for replicating workflows locally
What do you dislike about the product?
My wishlist would be:
- Finish the upgrade to v2 i.e. make workflows/pipelines first-class citizens. Especially at API level.
- Ability to chain workflows, i.e. have a workflow in one project trigger a workflow in another project, and wait for the result (having this work via the API is sufficient)
- Simpler docker-in-docker behaviour, avoiding having to choose machine: true when using e.g. docker compose or when building images.
- IDE integration (Webstorm/Intellij)
- Support for long-running flows (e.g. test suites that may take hours or even days to resolve)
- Support for running "failure" flows, e.g. for rollbacks
- More tooling for cloud services like AWS
- Finish the upgrade to v2 i.e. make workflows/pipelines first-class citizens. Especially at API level.
- Ability to chain workflows, i.e. have a workflow in one project trigger a workflow in another project, and wait for the result (having this work via the API is sufficient)
- Simpler docker-in-docker behaviour, avoiding having to choose machine: true when using e.g. docker compose or when building images.
- IDE integration (Webstorm/Intellij)
- Support for long-running flows (e.g. test suites that may take hours or even days to resolve)
- Support for running "failure" flows, e.g. for rollbacks
- More tooling for cloud services like AWS
What problems is the product solving and how is that benefiting you?
We use CircleCI for all our building, testing and deployment automation on AWS and elsewhere. The robust architecture and simple to use configuration make most common CI and deploment tasks extremely easy, and it is the best of the public multitenant CI systems that I have used.
Recommendations to others considering the product:
Read the docs thoroughly (focusing on newer docs). Install the local CLI. Write jobs in a composed manor (using commands, executors and orbs). Split jobs and make use of parallelisation.
Powerfull and accesible
What do you like best about the product?
It is easy to setup, use and navigate through the interface
What do you dislike about the product?
The web application can be cluttered sometimes in some sections like the workflows and running processes overloading you with information
What problems is the product solving and how is that benefiting you?
It helps us unify our pipelines and automate tasks
Great solution for android
What do you like best about the product?
Android docker image makes it easy to get up and running really quickly. Also better than self hosting like jenkins. Cloud solution is very convenient.
What do you dislike about the product?
Setting up android UI testing is kindda hard. It would be nice if there was a way to make it easier similar to bitrise
What problems is the product solving and how is that benefiting you?
Circle CI is great for my android builds and conveniently provides a docker image for android builds.
Effective Framework for Continuous Integration and Delivery
What do you like best about the product?
CircleCI has automated our post-commit testing, container image builds, and uploads to our image repository. The service is easy to administer and integrate with our tooling. During development, we get immediate feedback as to the health of the build, and whether a pull request is ready to merge into master.
The service's interface makes it easy to view the build history across branches.
The service's interface makes it easy to view the build history across branches.
What do you dislike about the product?
There's not much to dislike. The platform continues to evolve and is sufficiently flexible. It does require adding another asset in the form of a YAML file, and you are introducing yet another vendor dependency into your software delivery pipeline.
What problems is the product solving and how is that benefiting you?
Developing and deploying quality software relies on build automation and low-friction for testing. CircleCI's flexible tooling made it possible to automate these steps, ensuring changes are comprehensively tested and the pushed to the image repository. As a developer, it's very convenient.
Solid CI
What do you like best about the product?
It was easy to get going with Circle and tests now run fast
What do you dislike about the product?
No real downsides at this point that we have run into
What problems is the product solving and how is that benefiting you?
Circle is the basis of our continuous deployment pipeline handling linting, tests, and rollouts
Smooth onboarding
What do you like best about the product?
Well having tried out gocd to automate build-test-deploy pipeline, there were obvious issues with the self-hosted solution. The pipelines weren't as flexible as we needed. Moving to CircleCI was really smooth and the pipelines fits our requirement to a toe :)
What do you dislike about the product?
The UI mostly. I think in 2019 it could be alot better.
What problems is the product solving and how is that benefiting you?
Please look at what do you like the best.
circle ci fun
What do you like best about the product?
- reliability
- process for code review
- process for code review
What do you dislike about the product?
we have some flappers and need to re-run frequently
What problems is the product solving and how is that benefiting you?
code review process is smooth and automates some portion of review by running any changes through full test harness
Very advanced features, unintuitive interface
What do you like best about the product?
Lots of really great integrations. Also love that the config is stored in a file in your repository. Makes it much easier to copy config from one project to another and make modifications easily without dealing with a needless interface or permissions.
What do you dislike about the product?
The interface is confusing. Particularly when you run tests concurrently and are trying to get details on what failed. You have to view the artifacts from each run separately. And I still haven’t figured out how to rerun a single step that failed in the process. Buddy.works is much easier to use
What problems is the product solving and how is that benefiting you?
Continuous integration, automated testing and deployment, with alerts to our team on status.
Recommendations to others considering the product:
The best feature is the config file stored in your repository instead of having to use a web interface to make tweaks every time you need to adjust or start a new project
Good product, need more features
What do you like best about the product?
many things are already ready, just need to wire all the steps
What do you dislike about the product?
testing the pipeline can be a bit tedious.
What problems is the product solving and how is that benefiting you?
nothing special
showing 101 - 110