Command Palette

Search for a command to run...

Hectal
Phase 8Advanced9 of 9 in CI/CD

CI/CD at Scale: Tests, Monorepos, Releases & Metrics

A test strategy pipelines can trust (and what to do about flaky tests), CI for monorepos that only builds what changed, automated versioning and release notes, and measuring delivery with DORA metrics and pipeline observability.

A pipeline for one small service is easy. Hundreds of engineers, thousands of tests, and dozens of services sharing one repository are not: builds slow down, tests get flaky, releases become ceremonies. This phase covers the practices that keep delivery fast and trustworthy as you grow.

0/4 · 0%
4 topics ~29 min 7 code blocks & diagrams
Start with the first topic
1
8.1

Test Strategy in Pipelines & Taming Flaky Tests

Put the right tests at the right stage: many fast unit tests on every commit, fewer integration and contract tests on every PR, a few end-to-end tests before release. Then treat flaky tests as bugs, because a pipeline people don't trust gets ignored.

8 min 1 diagram 1 code practice

2
8.2

CI for Monorepos: Path Filters, Affected Builds & Remote Caches

In a monorepo, rebuilding and testing everything on every change doesn't scale. Path filters, dependency-aware 'affected' builds, and shared remote build caches keep pipelines fast while preserving the benefits of one repository.

7 min 1 diagram 1 code practice

3
8.3

Release Automation: Versions, Changelogs & Release Trains

Releasing should be a button (or nothing at all). Conventional commits and tools like semantic-release or release-please compute the next version, generate changelogs, tag, and publish, whether you ship continuously or on a release train.

7 min 2 code practice

4
8.4

Measuring Delivery: DORA Metrics & Pipeline Observability

You can't improve delivery you don't measure. The four DORA metrics show outcomes; pipeline metrics (duration, queue time, failure and flaky rates, cost) show where the pipeline itself slows teams down.

7 min 1 code practice