4 ms·

Speed, their main selling point. The default config uses a <del>8</del>2 core + 7.5g memory runner and capable to build simple projects in literal one minutes(i

Speed, their main selling point. The default config uses a <del>8</del>2 core + 7.5g memory runner and capable to build simple projects in literal one minutes(includes deploy) after you push even without cache. And it seems they maintain their own apt mirror or whatever, the package install speed looks unreasonably fast. But they currently only give 250 minute (default config) per week to free account now, probably due to the runner cost.

sciurus 6y ago
For anyone curious, the details on their OSS offering are at https://circleci.com/docs/2.0/oss/ https://circleci.com/docs/2.0/oss/ They give you 10,000 minutes of build time on their 2cpu/4gb workers per week with a max of 4 concurrent workers.
aeyes 6y ago
Free accounts on CircleCI only have access to 2 core runners and can't run multiple jobs in parallel. Most open source projects I have seen on Travis do matrix builds which will take much longer to finish due to this restriction. Edit: Looks like you get 4 concurrent jobs if you register as an open source project.
- charrondev 6y ago
  We pay for CircleCI at $WORK and it’s pretty good. You get up to 40x concurrency in the “Pro” plans and I’m sure you could work whatever you need into enterprise. My biggest complaint has been it lacks an very useful built in ability that Travis had, which is automatically running your builds on the merge of your current branch and target branch. You can right a script to do it yourself, but there missing some environmental variables to do it easily (because the build can start before the target branch is known).
  - Habbie 6y ago
    I can echo all of this - we also pay, we're very happy, the concurrency is nice (I believe they're bumping it to 80x soon - when my coworker asked "but what's the catch" I realised we pay by the CPU minute anyway so higher concurrency is a win for CircleCI -and- for US ;) ). I've also hacked about the 'merge' problem but it's not entirely satisfying. That all said, with GH actions currently being entirely free, and doing PRs better than CircleCI, we might shift our focus there.

sciurus 6y ago

For anyone curious, the details on their OSS offering are at https://circleci.com/docs/2.0/oss/ https://circleci.com/docs/2.0/oss/ They give you 10,000 minutes of build time on their 2cpu/4gb workers per week with a max of 4 concurrent workers.

aeyes 6y ago

Free accounts on CircleCI only have access to 2 core runners and can't run multiple jobs in parallel. Most open source projects I have seen on Travis do matrix builds which will take much longer to finish due to this restriction. Edit: Looks like you get 4 concurrent jobs if you register as an open source project.

charrondev 6y ago
We pay for CircleCI at $WORK and it’s pretty good. You get up to 40x concurrency in the “Pro” plans and I’m sure you could work whatever you need into enterprise. My biggest complaint has been it lacks an very useful built in ability that Travis had, which is automatically running your builds on the merge of your current branch and target branch. You can right a script to do it yourself, but there missing some environmental variables to do it easily (because the build can start before the target branch is known).
- Habbie 6y ago
  I can echo all of this - we also pay, we're very happy, the concurrency is nice (I believe they're bumping it to 80x soon - when my coworker asked "but what's the catch" I realised we pay by the CPU minute anyway so higher concurrency is a win for CircleCI -and- for US ;) ). I've also hacked about the 'merge' problem but it's not entirely satisfying. That all said, with GH actions currently being entirely free, and doing PRs better than CircleCI, we might shift our focus there.