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.
Great if you need heavier features, otherwise heroku's CI features work just fine
What do you like best about the product?
I love the automation of it. No issues with a developer forgetting to run a specific suite of tests, because you can't push without it. Also a little bit of public shaming when someone brakes the build is always fun.
What do you dislike about the product?
We have a super basic setup. A couple of projects, with basic unit test and only a team of 3 developers so it's just a little too heavy for us. I don't see the benefit of dealing with the confusing UI when the heroku CI github integration works just find and is all in the same place.
What problems is the product solving and how is that benefiting you?
Making sure we don't push broken code!
Recommendations to others considering the product:
Checkout heroku or Travis
- Leave a Comment |
- Mark review as helpful
Super awesome CI
What do you like best about the product?
Nice interface, realtime build logs, works with Ruby on Rails, rspec, and cucumbers. Integrates with Heroku and deploys after each successful build.
What do you dislike about the product?
Nothing to dislike. It's a free product, and does awesome stuff.
What problems is the product solving and how is that benefiting you?
Continuous integration in the cloud. Way better and easier than a custom built solution, and CircleCI solves that.
Recommendations to others considering the product:
It's one of the best cloud based CI tools out there.
CI SaaS done right
What do you like best about the product?
My three favorite features of CircleCI are the clean user interface, the ease of setting up parallelism, and the ease of configuration of builds. All three of these combined make CircleCI an experience that keeps me happy with their product.
What do you dislike about the product?
We would strongly like the ability for CircleCI to do our full continuous deployment, but we run our stack in a VPC at AWS, so this is not an option right now.
What problems is the product solving and how is that benefiting you?
We are solving for build automation, and have reaped this benefit tenfold. Our builds run faster and more stable than they ever did locally. We also trigger tasks like static code analysis and test coverage metrics upon build completion, which is an awesome thing to have automated.
Recommendations to others considering the product:
Definitely give their free trial a spin, but I don't doubt you will be extremely pleased. Make sure to try out all aspects, not just test running / build automation, but also delve into making your own configuration file and triggering tasks based on build events. This will give you the full experience and a good idea of the effort required for setup within your organization. Don't just take my word for it.
Circel Ci is easy to integrate and use with cool UI/UX
What do you like best about the product?
Circle Ci is easy to use, integrate and have cool UI.
I mostly love all the feature of it.
It also provide 1 free container that is good for open source project. Open source project owner can be use this Circle Ci integration tool easily.
I mostly love all the feature of it.
It also provide 1 free container that is good for open source project. Open source project owner can be use this Circle Ci integration tool easily.
What do you dislike about the product?
Some times it's take a lot of time for test a build, i think it can make faster.
What problems is the product solving and how is that benefiting you?
Continuous Integration for the product and Apps are easy to achieve with circle ci.
[Ci skip] is also supported by circle Ci so if we don't want to run CI for documentation releated code then it's make easy to use.
[Ci skip] is also supported by circle Ci so if we don't want to run CI for documentation releated code then it's make easy to use.
Good consistent CI
What do you like best about the product?
Good UI, all the most common and expected features of a CI tool.
Slick UI with a great UX. Fast builds. One free build container.
Slick UI with a great UX. Fast builds. One free build container.
What do you dislike about the product?
No bitbucket support. No open source free projects. No obvious way to encrypt secrets (a little confusing documentation).
What problems is the product solving and how is that benefiting you?
Continuous integration.
Recommendations to others considering the product:
Look at Travis CI and CodeShip first. These all have similarities, but the other two are preferred for me.
great CI tool
What do you like best about the product?
the ability of ssh into vm/containers is really amazing, since it allows you to easily debug CI configurations and reduce executions trying to fix that configuration
What do you dislike about the product?
It does not have ability to integrate with bitbucket
What problems is the product solving and how is that benefiting you?
CI and CD.
The developer of the initial landing
What do you like best about the product?
This service is directly integrated with GitHub, the developer of the initial landing, CircleCI will scan its application in GitHub containers. After a simple installation process, if you need to guide the developer on how to compile and deploy. Every time the preparation of the code, CircleCI will automatically compile the application, automatic test, if the user is using a similar TestFlight tools, CircleCI will automatically apply the deployment. CircleCI was founded by Biggar Paul and Rohner Allen. Biggar received a PhD in computer science and worked at Mozilla.
What do you dislike about the product?
Simply say. In the first machine node, I specify the JDK version of JDK Oracle 8 (the default is OpenJDK 7). Then added a ANDROID_HOME of the environmental variables point to the location of the SDK Android (TMD, since you are in the document have said SDK Android in this path, it does not give me a good environment variable).
What problems is the product solving and how is that benefiting you?
Dependencies node, if it recognizes that you are a Gradle project, by default it is just dependencies gradle. So the result is obvious - at least to put the SDK Build-tools Android installed on it XD
Yes, its own version of Gradle is 1.10, a little old. And habits we should use their wrapper to run the (Travis Ci at this point is very good, if the judge to the wrapper./gradlew will use your project to run, and is not a system gradle command).
Yes, its own version of Gradle is 1.10, a little old. And habits we should use their wrapper to run the (Travis Ci at this point is very good, if the judge to the wrapper./gradlew will use your project to run, and is not a system gradle command).
Engineering lead on an open source project using CircleCI
What do you like best about the product?
I don't have to host it and it's free for open source projects. For a relatively simple (dependency-wise) Go project with a good suite of unit tests, it was easy to get running, integrated with GitHub to ensure every PR was passing our unit tests. Once it's all configured it's great, it just works.
What do you dislike about the product?
YAML configuration files are kind of a pain. The available database services seem to be targeting a cross section of technologies and outside of the old school core RDBs (MySQL, PostgreSQL), hit a mix of highly used, and kind of esoteric options (do they have a lot of Neo4j or Riak users?). It would be nice to see a few more options available (we have a RethinkDB integration, hint, hint...) because I'm not going to pick my services because the CI system supports it, I'm going to pick a CI system because it supports my services.
What problems is the product solving and how is that benefiting you?
Automating test runs against all submitted PRs. We later added a CodeCov integration and we submit coverage analysis from CircleCI over to CodeCov. That visibility helped us raise our test coverage from ~55% to ~75% over about 3 months, all through small, less than 1%, bumps in coverage with each PR merged to master.
Recommendations to others considering the product:
If you're test and build environments are relatively straightforward, it's a good tool. However other solutions are easier to work with as your setup becomes increasingly complex.
small team tested
What do you like best about the product?
The docker integration is super handy when I'm lucky enough to have a side project built that way. I have used it without docker for smaller projects too... I even think that is better than Travis, but my experience is less deep there. The setup is painless
What do you dislike about the product?
The interface is a bit sparse in an unhelpful way. Either the text and elements could be bigger, or more could be added. I don't often use the web interface, but when I do it's a "meh" experience.
What problems is the product solving and how is that benefiting you?
We use it for small client projects with private repos and few specs along with developing larger internal services in docker environments.
Recommendations to others considering the product:
I think it's the best built-in CI for docker environments I've used so if that applies to you it might be worth switching.
Continuous Integration flexible and modern
What do you like best about the product?
You pay for containers so you can have lots of projects running their integrations in the same container, in that sense is cheaper than TravisCI service, and generate the .circle.yml file on the repo can be done too on the UI
What do you dislike about the product?
I didn't found shell tools for check the .yml syntax of the .yml file though the alternative of being generated by the web is cool.
What problems is the product solving and how is that benefiting you?
It was a travel company with lots of subsystems and apis connected, so continuos integrations of these apis was critical in order to don't have downtimes, or bugs that can interrupt the service
showing 461 - 470