CI Pipeline Design
By Wei · Published · Updated
Fast enough that nobody looks for the skip-ci flag.
Tags: Engineering, Technical, Productivity
Prompt template
## CI pipeline - Project: [textarea: Language, framework, repo structure] - Pipeline today: [textarea: Each step and how long it takes] - Test suite: [textarea: Types of tests and their runtimes] - Platform: [dropdown: GitHub Actions, GitLab CI, CircleCI, Jenkins, Buildkite] - Team size and commits per day: [text: Both] - What hurts: [multi: Too slow, Flaky tests, Unclear failures, Expensive, Blocks releases] Order the stages so the fastest checks fail first. Tell me what can genuinely run in parallel and what cannot. Caching strategy for dependencies and build artefacts. What runs on every commit versus only on main. Deal with flaky tests as flaky tests rather than adding retries everywhere and calling it fixed. Give me a target total runtime and say what to cut to reach it.