ci-cd – Page 21 – Türker Yıldırım

Failing on a growing baseline, which is the whole ratchet

NoteDecember 10, 20192 min read

A baseline that can grow is a suppression file, and a baseline that can only shrink is a debt that gets paid — the difference is one CI…

A baseline is what makes static analysis adoptable

Deep diveDecember 10, 201914 min read

0.12 shipped in December and the ignoreErrors list can be deleted. A generated debt register, a ratchet that only shrinks, and a level to stop at.

A GitLab CI rules block replaces only/except

NoteNovember 27, 20192 min read

only and except could not be combined coherently — specifying both applied them independently and produced results nobody predicted. First-match-wins ordering is what makes rules comprehensible where the…

Static analysis on changed files in a pre-commit hook

NoteNovember 14, 20191 min read

A full analysis on a large codebase takes long enough that nobody runs it before committing, so every finding arrives from CI after the context has been lost.…

TypeScript on a JavaScript codebase, one file at a time

Deep diveNovember 8, 201910 min read

3.7 shipped optional chaining in November and the objection got smaller. allowJs, checkJs and a per-file opt-in — and strictNullChecks, which is the flag that pays.

Fatal errors that reach a person before they reach a customer

Deep diveOctober 2, 201910 min read

The error tracker had 400,000 events and nobody had opened it in a month. Alert fatigue, in the one tool that exists to prevent it.

Laravel 6 adopted semver, and the upgrade got boring

Deep diveSeptember 25, 20199 min read

5.8 to 6.0 is a smaller change than 5.7 to 5.8 was, which is the point. What semver means for a framework, and what LTS actually promises.

Coverage of changed lines, rather than of the codebase

NoteSeptember 19, 20191 min read

Total coverage moves so slowly that it says nothing about the change in front of you, and the question a reviewer actually has is whether the new code…

Kubernetes is not the answer to this question

Deep diveSeptember 16, 201915 min read

The question was how to deploy four services, and the answer arrived before it. Naming what you actually need — scheduling, health, rolling deploys, secrets.

A CI job that only runs when the files it cares about changed

NoteSeptember 10, 20192 min read

A monorepo pipeline that runs every job on every push spends most of its minutes proving that unchanged code still works. The trap is that changes compares against…