A minimal CI pipeline in 200 lines
No plugins, no marketplace, no YAML sprawl. Just a runner, a queue, and honest logging.
The pipeline is a queue table, a worker loop, and a log file per job. Everything else is convention.
What it loses in features it gains in debuggability. When a job fails, the log is a text file on disk, not a web UI you have to page through.
It has been in production for eleven months across four repositories.
#ci#tooling#simplicity
More in this section
🔒softwareSubscriber
The quiet return of single-file binaries
Static linking is fashionable again. The reasons are less about performance and more about deployment fatigue.
🔒softwareSubscriber
Editorial: your dependency tree is a supply chain
Treat it like one — pin, audit, mirror, and stop trusting transitive installs by default.
🔒softwareSubscriber
WebAssembly outside the browser: what actually shipped
Five years of plugin runtimes, edge functions and one very large migration.