External reviews
489 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Good for small to medium sized projects, not ideal for large projects with artifacts to deploy
What do you like best about the product?
CircleCI is easy to set-up. It typically automatically can detect the best way to run most types of projects -- both Ruby on Rails and Java.
What do you dislike about the product?
CircleCI makes it difficult to get a comprehensive view of what tests are running vs. what tests have run on each branch or remote. Compared to other tools I've used -- like TeamCity -- It feels like you really have to go searching to understand what's happening with your builds. It's not easy to see in one place what builds are in the queue, what the success vs. failure trend has been over several builds, or even to understand what builds have run longer than others or why. In addition, CircleCI is not as flexible when it comes to dependencies between projects, or using CircleCI to perform automated deployments. Finally, my biggest concern is that CircleCI seems to perform slowly -- it feels very slow and clunky to go from screen to screen.
What problems is the product solving and how is that benefiting you?
We wanted a way to run automated unit tests for all of our projects without having to maintain our own CI servers. CircleCI handles all the infrastructure so we don't have to.
Recommendations to others considering the product:
Consider whether you really need a cloud-based option, or if you would be fine with maintaining your own install. There are other options -- TeamCity, for example -- that are more robust and free for the same size projects that CircleCI is aimed at.
Almost all CI software gets more expensive when you need more build agents, and CircleCI is no exception. Consider the value you're getting when you add more agents on CircleCI vs spending a similar amount of money on other options that are more flexible that have the trade-off of requiring you to maintain your own install.
Almost all CI software gets more expensive when you need more build agents, and CircleCI is no exception. Consider the value you're getting when you add more agents on CircleCI vs spending a similar amount of money on other options that are more flexible that have the trade-off of requiring you to maintain your own install.
Great platform that has worked for us
What do you like best about the product?
CircleCI makes it easy to rapid setup up continuous build, integration and deployment environments. Our needs are pretty basic in this regard, but it seems to support everything out of the box.
What do you dislike about the product?
The "my account" interface is a little bit hard to navigate and sometimes I find myself getting lost with where I am in the settings and what github org is the information on the page referring to.
What problems is the product solving and how is that benefiting you?
We wanted a way to automate all of code building, integration, and deployment to make our processes more scalable.
Using it with Rails
What do you like best about the product?
I love the simplistic user interface and the notifications on web. I appreciate the intergration with github and easy of install with Rails. The open pull request button is so handy now!
What do you dislike about the product?
The service is very similar to other services and needs to find a way to individualize from other competitors.
What problems is the product solving and how is that benefiting you?
Running tests, and saving time, improving quality for the application.
Recommendations to others considering the product:
That is is easy for setup and has a great free plan. We also use the two container plan to increase speed of builds.
It works fine, i miss a nicer UI.
What do you like best about the product?
I like the configuration options. They fit nicely mi way of thinking.
I like just so much the inference engine. Sometimes I would like to be able to get rid of it.
I like the github integration where users don't have to create a CircleCi specific account, and they just login with their github user.
I like just so much the inference engine. Sometimes I would like to be able to get rid of it.
I like the github integration where users don't have to create a CircleCi specific account, and they just login with their github user.
What do you dislike about the product?
Sometimes I would like to be able to totally disable the configuration inference.
What problems is the product solving and how is that benefiting you?
We work with several concurrent projects, and making sure that every single commit and PR is being tested is super helpful.
Recommendations to others considering the product:
Better support for building through docker, I miss docker images caching between builds.
Nearly complete solution for Continuous Integration
What do you like best about the product?
1. Easy to setup for developers
2. Ability to spin up different repos efficiently
2. Ability to spin up different repos efficiently
What do you dislike about the product?
1. Lack of integrations with different hosted git repository options
2. Containerization of processes is a bit clunky and depends too much on the AWS infrastructure being up or down
3. Ability to parallelize should be docker or container based - not VM based.
2. Containerization of processes is a bit clunky and depends too much on the AWS infrastructure being up or down
3. Ability to parallelize should be docker or container based - not VM based.
What problems is the product solving and how is that benefiting you?
My team needed a solution that allowed it to spin up a continuous integration process without the headache of setting up and maintain different CI Solutions. CircleCI has filled this gap fairly well.
Unfortunately, it's great for smaller teams and I can't see it scaling to enterprise-level support or needs as the cost would be completely prohibitive.
Unfortunately, it's great for smaller teams and I can't see it scaling to enterprise-level support or needs as the cost would be completely prohibitive.
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
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.
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).
CircleCI
What do you like best about the product?
Very easy to get started, you are able to add custom steps
What do you dislike about the product?
Hard to do multi-stage integrations - ie unit tests followed by integration tests
What problems is the product solving and how is that benefiting you?
software developing - able to find bugs/breaks in software faster
Like the UI, hard to setup
What do you like best about the product?
UI, ability to restart builds, jump through different builds
What do you dislike about the product?
Only runs on docker 1.8 (as of about a month ago) that made us move away from circleci.
What problems is the product solving and how is that benefiting you?
Continuous deployment, and precommit checks.
Works with most tools that we've used, hooks into different ecosystems like github/ aws.
Works with most tools that we've used, hooks into different ecosystems like github/ aws.
Recommendations to others considering the product:
It is hard to understand setting up hooks to github repos/ other ecosystems, take some time to understand it better.
showing 41 - 50