Guides

Answers to the questions teams ask about repeated CI work. Each guide starts with the options that need no new tool, then shows where hushrun fits.

Run fewer checks

• Skip CI when the code hasn't changed: commit messages, path filters and comparing the code itself, and what each one misses.
• Why CI runs the same tests twice: the routes that lead the same code to CI again, and how to close each one.
• Reduce your GitHub Actions costs: fewer runs, shorter runs and cheaper minutes, in that order.
• Cache test results across machines: what Gradle, Bazel, Nx, Turborepo, Vitest and Jest really cache.
• Keep CI useful with coding agents: check before the push, and reuse the result in CI.

Ship one artifact

• Build once, deploy many: what the practice means, what it asks of your build, and how to do it.
• Promote a Docker image between environments: copy an image by digest, without a rebuild, and prove what you deployed.

Choosing a tool

hushrun and the alternatives sets hushrun beside Nx Cloud, Turborepo, Bazel, Kargo and JFrog Artifactory.