3 ms·

I've switched my personal projects, and my employer has switched to Circle over the past year. Circle's dockerized strategy for building up your CI/CD platform

I've switched my personal projects, and my employer has switched to Circle over the past year. Circle's dockerized strategy for building up your CI/CD platform means that they support the new version of X nearly the day it comes out. Historically Travis has been very slow at this. Their support for Postgres 10 was an embarrassment (https://github.com/travis-ci/travis-ci/issues/8537 https://github.com/travis-ci/travis-ci/issues/8537). It's also vastly easier to parallelize your test suite. With Travis we had to install a third party gem to run our Rails' across many nodes. We also had to hand-manage balancing. With Circle we simply followed the docs, and we're off to the races.

ArturT 8y ago
I work on knapsack gem to split tests across parallel CI nodes. To do optimal balancing I developed a dynamic test suite split with Queue approach. Here is example for Travis CI https://docs.knapsackpro.com/2018/how-to-run-travis-ci-parallel-jobs-with-build-matrix-feature-fast https://docs.knapsackpro.com/2018/how-to-run-travis-ci-paral... And this is the graph showing the difference if you compare knapsack_pro dynamic tests split with what CircleCI does which is basically only time-based split. https://docs.knapsackpro.com/2018/improve-circleci-parallelisation-for-rspec-minitest-cypress https://docs.knapsackpro.com/2018/improve-circleci-paralleli...
- obfk 8y ago
  +1 for Knapsack. It's cumulative savings for our CI/CD has been tremendous.