Slow, frustrating, and wasteful CI/CD pipelines interrupt developer flow and have a negative environmental impact.
The 'ritual' antipattern involves wastefully running identical, comprehensive pipelines for pull requests, merges, and nightly schedules.
Create context-specific pipelines for different triggers and use path filtering to run only the jobs relevant to the code that has changed.
The 'hoarding' antipattern wastes storage and makes navigation difficult by keeping every build artifact indefinitely instead of using automated cleanup.
Prioritize tests that are most likely to fail, such as integration tests, to get feedback faster instead of following a conventional testing pyramid order.
Replace a single, long-running sequential pipeline with multiple parallel jobs for independent components like frontend and backend to significantly reduce wall-clock time.
Leverage caching for dependencies, build outputs, and Docker layers, and use pre-built tooling images to avoid starting from scratch on every run.
Avoid race conditions where concurrent pipelines overwrite shared resources like a 'latest' tag by using unique identifiers like the Git SHA for artifacts.
Ensure build agents are at least as powerful as developer machines to prevent resource-related failures, and consider self-hosted runners for full control over hardware.
A summary of common pipeline pitfalls and the corresponding best practices for creating faster, more reliable, and efficient CI/CD workflows.
50:28Zan Markan
39:49Mustafa Toroman
24:31Daniel Tao
32:29Martin Beránek
56:19Pawel Piwosz
29:49Lian Li
21:39Johannes Hansen
23:33Tamás Bazsonyi
Jobs that call for the skills explored in this talk.
Atruvia AG
Berlin, Germany
smartclip Europe GmbH
Hamburg, Germany
CONTIAMO GMBH
Berlin, Germany
