kiln.config.js
README.md
build.log
1
2
3
4
5
6
7
8
9
// an open-source build cache
Builds that only ever run once
Presented by {{author}}
main · Ln 3, Col 5 · UTF-8
01
Why your builds keep repeating
02
How Kiln caches a build
03
Moving a pipeline over
04
Numbers from real teams
05
What comes next
@@ THE PROBLEM @@
Kiln builds it once and shares the result with everyone.
Every pull request starts from a clean machine. It downloads the same packages, compiles the same files and runs the same tests that passed an hour ago.
Nothing changed, but you still wait.
build.log
// PART TWO
hash.ts
Source, lockfiles and flags become one fingerprint.
01
store.ts
Laptops and CI read from the same remote store.
02
run.ts
Only steps with a new fingerprint actually run.
03
Point Kiln at your inputs and outputs. It handles hashing, storage and restore.
import { defineCache } from 'kiln';
export default defineCache({
inputs: ['src/**', 'package.json'],
command: 'npm run build',
outputs: ['dist/'],
remote: 'https://cache.kiln.example',
});− before · 14 min
+ after · 40 sec
steps:
- run: npm ci
- run: npm run build
- run: npm teststeps:
- run: npx kiln restore
- run: npx kiln run build
- run: npx kiln run test// BY THE NUMBERS
faster warm builds on the average pipeline
of CI steps restored straight from cache
builds skipped by teams last month
v0.1
A weekend hack that cached one monorepo
v1.0
Remote cache shared across laptops and CI
v2.0
Builds split across machines automatically
next
Editor plugins and a live cache dashboard
CHANGELOG.md
Ines Marlow
Platform lead, Fernhill Labs
Maya Lindqvist
Core and hashing
Jonah Okoro
Remote storage
Priya Sethi
CI integrations
Tomás Alves
Docs and community
kiln.example
hello@kiln.example
$ curl -fsSL https://kiln.example/install | sh
$ kiln init
$ kiln run build
# restored from cache in 0.4s