Overall Satisfaction with CircleCI
We use CircleCI for most of our development workflows. Building, testing and deploying. We use it across most teams and departments.
It integrated nicely with GitHub and we are able to validate every change on every branch before merging and automatically deploying to production. I use it for both Ruby and React projects.
It integrated nicely with GitHub and we are able to validate every change on every branch before merging and automatically deploying to production. I use it for both Ruby and React projects.
- Shows a clear workflow diagram and be able to re-run specific steps.
- Fast set-up integration with GitHub.
- Jobs can sometimes take too long.
- Documentation on how to set up could be improved.
- Simple continuous integration for every branch before merging for safety.
- Simple continuous deployments means better velocity.
CircleCI is a sass product which means you don't need to maintain your own servers. This can also be a negative as you are dependent on their service. This also means you can't ssh into a machine to see what went wrong like you can with Jenkins. However for most users this isn't needed and CircleCI's SLA is fine and there is a lot of community info on the internet to solve issues you might be having.
Do you think CircleCI delivers good value for the price?
Yes
Are you happy with CircleCI's feature set?
Yes
Did CircleCI live up to sales and marketing promises?
Yes
Did implementation of CircleCI go as expected?
Yes
Would you buy CircleCI again?
Yes