Pipelines & Build

Pipelines are container jobs attached to a site — build, release, migrate, anything — run off-host on a hosted build service.

Concepts

• Pipeline — a named job defined in your repo’s pipeline manifest.
• Image — the container image a pipeline runs in.
• Variable — pipeline-scoped configuration.
• Run — one execution of a pipeline. One run is in flight per pipeline at a time, keeping state predictable.

Manifest sync

Pipeline definitions live in your repository (e.g. .podmaker/pipelines.yml) and are synced read-only into the panel — the repo stays the source of truth. Push to change a definition; the panel reflects it.

Triggering

A run can be triggered from:

• the panel button,
• a webhook, or
• the API.

The hosted build service

The build-service executes runs on a pool of workers. In production it uses a Firecracker micro-VM runner for isolation, with:

• cache volumes to keep repeat builds fast,
• private registry integration for pulling and pushing images,
• network and timeout controls per run.

Log lines stream live to the panel over SSE; artifacts and images land in your registry, and run history supports retries.

→ Marketing overview: Pipelines & Build