22 engineers on Hacker News describe using CircleCI first-hand: 5 endorse it, 6 regret it, 2 are mixed.
“we got an opaque email from CircleCI about their new `performance plan` which would have increased the cost to $300/mo.”
regret · production · juanbyrge · 2022-12-08 · source ↗ · wrong label?“it left a bad taste in my mouth and we moved to Jenkins a couple months later”
regret · production · nerdjon · 2022-04-06 · source ↗ · wrong label?“we migrated from CircleCI because they were screwing up their UX”
regret · production · stickfigure · 2022-04-05 · source ↗ · wrong label?“we had major issues with just paying for it via CircleCI. Excessive downtimes, a UI so slow it was nearly unusable”
regret · production · mdeeks · 2021-06-03 · source ↗ · wrong label?“CircleCI improved by leaps and bounds in 2020, and the new Circle pipeline view equivalent is even better”
endorse · production · gerhardlazu · 2020-12-27 · source ↗ · wrong label?“We moved to CircleCI and while I have many frustrations with it, the cost is minimal compared to the developer time.”
mixed · production · danpalmer · 2020-11-02 · source ↗ · wrong label?“We switched to CircleCI and it did everything we needed and we never had to lose half a day to CI problems again.”
endorse · production · eeeeeeeeeeeee · 2019-04-30 · source ↗ · wrong label?“With CircleCI you can provide your own custom Docker image for running the build.”
endorse · production · vishnu_ks · 2019-01-23 · source ↗ · wrong label?“With CircleCI the solution we use is really hacky.”
regret · production · marcinzm · 2018-12-07 · source ↗ · wrong label?“Circle CI 2.0 and their triggered deploys work pretty well, actually.”
mixed · production · 2 yr · busterarm · 2017-12-18 · source ↗ · wrong label?“CircleCI is amazing. We use it and it seems to offer us everything we need in a very nice shiny box.”
endorse · production · gurgus · 2016-12-20 · source ↗ · wrong label?“We couldn't replicate this stage->master promotion/rollback in CircleCI.”
regret · production · philip1209 · 2015-04-04 · source ↗ · wrong label?“We switched to CircleCI from our own, painfully maintained Jenkins box to test our Rails apps.”
endorse · production · rsanders · 2013-09-24 · source ↗ · wrong label?“This solution was born when trying to do native builds on CircleCI”
neutral · production · zamalek · 2024-02-07 · source ↗ · wrong label?“I'm always experimenting with other options, which has recently included GHA and Circle.”
neutral · personal · 013a · 2019-09-20 · source ↗ · wrong label?“CI is done through CircleCI.”
neutral · production · dmlittle · 2018-12-31 · source ↗ · wrong label?“My era of tinkering ended once we moved to CircleCI.”
neutral · production · bm1362 · 2017-10-10 · source ↗ · wrong label?“We switched over from Circle and it's been awesome”
neutral · production · NightMKoder · 2017-02-01 · source ↗ · wrong label?“We use circle for continuous integration”
neutral · production · itajaja · 2016-12-12 · source ↗ · wrong label?“We've got support on great CI systems like circleci and scrutinizer-ci.”
neutral · production · bkanber · 2015-06-08 · source ↗ · wrong label?“by calling pronto from CircleCI.”
neutral · production · dankohn1 · 2015-03-08 · source ↗ · wrong label?