Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
CircleCI is very good tool but there're some problem with on-premises
What do you like best about the product?
I can write the configuration for CircleCI very easily.
And I can login to the build job container using SSH, this is a big advantage than Jenkins.
I also manages Jenkins cluster. With Jenkins, users want us to install plugins they want to use.
CircleCI uses containers to build each jobs so users can install any dependencies of their application even if it is a system components like glibc.
Also, other users using CircleCI can login to their job.
This means the user can do trouble shooting by their selves. This is a big advantage than Jenkins, too.
And I can login to the build job container using SSH, this is a big advantage than Jenkins.
I also manages Jenkins cluster. With Jenkins, users want us to install plugins they want to use.
CircleCI uses containers to build each jobs so users can install any dependencies of their application even if it is a system components like glibc.
Also, other users using CircleCI can login to their job.
This means the user can do trouble shooting by their selves. This is a big advantage than Jenkins, too.
What do you dislike about the product?
We're using CircleCI enterprise on our on-premise servers, not AWS.
With this environment, we cannot use docker on CircleCI Jobs.
This means we cannot build Docker images on CircleCI, need to prepare other docker host to build them...
With this reason, I cannot recommend to use CircleCI to my colleagues in my company.
All features except docker related issues are very good so this is very, very disappointment thing...
With this environment, we cannot use docker on CircleCI Jobs.
This means we cannot build Docker images on CircleCI, need to prepare other docker host to build them...
With this reason, I cannot recommend to use CircleCI to my colleagues in my company.
All features except docker related issues are very good so this is very, very disappointment thing...
What problems is the product solving and how is that benefiting you?
I'm testing and building my application on CircleCI.
I can test my application with very easy YAML formatted configuration file.
The jobs are run in containers, separated environment. so there's no problems related with other jobs.
I also release my application if the git branch is master.
We can use manual approval in the CircleCI workflow, it makes us being able to use CircleCI for Continuous-Deployment with production release.
I can test my application with very easy YAML formatted configuration file.
The jobs are run in containers, separated environment. so there's no problems related with other jobs.
I also release my application if the git branch is master.
We can use manual approval in the CircleCI workflow, it makes us being able to use CircleCI for Continuous-Deployment with production release.
Recommendations to others considering the product:
CircleCI is very good tool to do Continuous-Integration or Continuous-Delivery if you can use circleci.com or run CircleCI Enterprise on AWS.
If you want to run your on on-premise servers, it causes some painful situation.
If you want to run your on on-premise servers, it causes some painful situation.
- Leave a Comment |
- Mark review as helpful
A solid, reliable and fast CI host
What do you like best about the product?
It just works and can handle anything we throw at it
What do you dislike about the product?
The UI is not as feature-rich as TeamCIty.
What problems is the product solving and how is that benefiting you?
Running hundreds of build each day across many branches of many code repositories across Linux and Mac platforms for web apps, micro-services and React Native iOS and Android products.
Recommendations to others considering the product:
You need special agents if you wish to build xcode
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
it's an amazing tool to test and integrate with teams
What do you like best about the product?
I like the way about CircleCI do the pipelines and implement integrations with the commits that every single member of the team do every single time, also I like the way about CircleCI share you the errors in case of exists
What do you dislike about the product?
when I try to use the mobile app, I can't see anything information about the projects and I would like to improve that application because sometimes I don't have a PC close to me and I haven't a clear way to see the errors instead of a mail or the pipelines in the platform
What problems is the product solving and how is that benefiting you?
with CircleCI I found information about integration, commits and features that if the pipelines would not exists, I'm sure that would be causing problems in the production app at the time of deployments
Recommendations to others considering the product:
take the time to start an example guide about integrations and other things that are neccessary to understand how to use and how works the tool
CI for everyone
What do you like best about the product?
I had a good experience with Circle CI/CD platform and would recommend it to everyone.
What do you dislike about the product?
It was a company account and when the person who set it up left all jobs came to stop.
What problems is the product solving and how is that benefiting you?
Every commit is potentially a release candidate. CircleCI streamlines the process of deployment.
Recommendations to others considering the product:
Consider your commits as release candidates and CI/CD as automatic way to deliver those candidates into production environment. CI/CD tools greatly help to minimize Lead Time KPI.
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.
Your Friendly CI tool
What do you like best about the product?
Fast Builds, Developer-Driven Configuration, User-Friendly
What do you dislike about the product?
Limited support for Mobile and web integrations.
What problems is the product solving and how is that benefiting you?
Continuous Deployment, Ensuring High Release Quality.
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 tool, easy to set up
What do you like best about the product?
We like how easy it was to integrate CircleCI to our project and set up with Cypress.
What do you dislike about the product?
Figuring out ho to do cache invalidation took some time.
What problems is the product solving and how is that benefiting you?
We use CircleCI to run tests. We integrated CircleCI into our GitHub and run a CircleCI job on every commit to the branch
We used CircleCI last few years. But now we considering move to github action.
What do you like best about the product?
I think CircleCI most powerful feature is macOS hosting. I was use to Jenkins. But it needs macOS server to using iOS. We are using AWS but unfortunately AWS doesn't support macOS. So CircleCI was good alternative.
What do you dislike about the product?
Sometimes It is hard to find out build error on CircleCI. I had a few experiences that fail build. So we are considering move to Github actions.
What problems is the product solving and how is that benefiting you?
CircleCI was almost all solution about CI including macOS support. Specially I liked simple usage through yml.
showing 181 - 190