Creating efficient, convenient and reliable CI
summary
Concrete CI practices for reliable builds: make pipelines idempotent and measurable by tracking queue and execution times; use Git tags plus automatic semantic versioning via git-describe and a Gradle plugin so merges produce release tags (demo shows auto-jump to 0.91). Prefer prebuilt images and pinned tool versions, avoid monorepos, use GitLab features (interruptible jobs, allow_failure), share a Gradle distribution on runners to save ~145 MB and ~16s per build, and use short-lived support branches for hotfix rollbacks.
AI-written summary · about
chapters (10)
- 0:00CI automation intro
- 2:35Ideal CI features
- 7:32Nine CI principles
- 13:55Cache and tool optimization
- 21:17Versioning without commits
- 30:14Generic CI pipeline phases
- 39:31Avoiding Monorepo builds
- 52:49Caching build dependencies
- 57:46Cactus Based Development in Git
- 1:01:21Summary & Q&A
related talks
24mCI/CD Best Practices to Deliver Software Faster
32mPractical Tips & Tricks for CI/CD Success
26mOptimizing Your CI Pipelines
32mBuilding Confidence Together: Continuous Integration & Testing
48mDemystifying CI/CD
41mContinuous Integration Tips & Tricks
30mContinuous Integration; Tips & Tricks
01h 29mKeeping Your CI–CD Pipeline as Fast as it Needs to Be