Dockerised local build and testing environments made easy
summary
Argues that using containers for both build and test gives repeatable local and CI results and shows batect as the tool used instead of Docker Compose, with a wrapper script checked into each repo, task metadata, healthchecks and Docker networking to start dependencies in order. Claims adoption by dozens of teams and a ThoughtWorks Tech Radar trial rating, measures a cold VM setup at 30m04s and a warm run where batect is 17% faster than compose, notes Google found 84% of CI failures are environmental.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 3:37Build vs testing environments
- 10:38Build environment with Protekt
- 13:05Testing terminology explained
- 17:15Testing environments with Protekt
- 22:34Protekt vs Docker Compose
- 26:26Next steps and resources
related talks
05mInstant Self-contained Development Environments
21mMaking Reproducible Builds Faster with Docker Bake
41mThink Cloud, Develop Locally
50mInstant Self-contained Development Environments for Everyone
10mBoost your productivity and confidence with Docker -
26mTales from the QA Crypt
50mInstant Self-contained Development Environments for Everyone
29mDeveloping JS Applications Using Docker Containers