We use CircleCI as a pre-check on commits, before doing the actual code review, integrated to phabricator. As our codebase grows, running lint checkers and tests locally before opening a code review takes a long time, so we usually do not do it locally and leave it to the CI, trading our time in running automatic checks for focusing on other tasks. It also help us locate adjusts to our commits before the actual code review, the CI will indicate and error on the commit and not send it to the next step, peer review. Review collected by and hosted on G2.com.
I am not in charge of configuration and maintenance of the CI on my company, but sometimes we have problems where the automation stops working, sometimes it would run the tests we delegated to it but not make a post-test change on the commit status (would not change it to ready to review) Review collected by and hosted on G2.com.
