Marcin chose to use CircleCI because he was most familiar with it compared to other continuous integration tools. His teammates had also used CircleCI successfully in previous roles. Additionally, CircleCI offered strong native Docker support and caching capabilities as well as recommendations from an experienced user. Marcin's CircleCI workflow involved running tests using a custom Docker image, building images, and deploying to Heroku with potential optimizations like sharing images between jobs and speeding up tests through parallelization.

1. How we use CricleCI in Laterallink?
Marcin Prokop

2. Why I decided to go with CircleCi?
I know this best among others CIs …
As my gun in the Army

3. Why I decided to go with CircleCi?
My teammates have experience with it in the previous
companies

4. Why I decided to go with CircleCi?
Strong support from a guy who uses it heavily (ex. Google,
FB former) and sits next to me :P

5. Why I decided to go with CircleCi?
Native Docker support + cache

6. Flow

7. Flow

8. Run tests using deliveroo/circleci image
CircleCi config docker-compose.ci.yml

9. Build images

10. Deploy to Heroku

11. Possible optimizations
Sharing docker image between jobs by remote repo

12. Possible optimizations
Speedup tests
• use parallel_tests gem
• spread tests across multiple jobs