Deploys
The history behind every target — what was built, from which commit, and how to go back
Every release of an app or site target is a deploy: a row with the image or bundle it produced, the commit it came from (when it came from one), who triggered it and the build log.
pier deploys ls api
STATUS TYPE RESOURCE ENV COMMIT MESSAGE CREATED
succeeded app api prod da2b... fix(configdiff): a volume binding is ... 26s ago
superseded app api prod zot.pier-registry.svc.cluster.local:5... 1m ago
superseded app api prod zot.pier-registry.svc.cluster.local:5... 2m ago
succeeded app api prod da2b... fix(configdiff): a volume binding is ... 3m ago
| Status | Means |
|---|---|
pending | waiting for a build to finish |
building | the build is running (pier deploys logs <id> streams it) |
succeeded | built and rolled; the target runs this deploy |
failed | the build or the roll failed; the previous deploy keeps running |
Commands
| Command | Does |
|---|---|
pier deploys / pier deploys ls [<ref>] | the history, newest first |
pier deploys info <id> | image, commit, author, timing, strategy |
pier deploys logs <id> | the build log |
pier rollback <ref> [--to <id>] | run a previous deploy's image or bundle |
Behaviour
- A deploy never changes variables; a rollback runs an older image with the current environment version.
- Deploys are kept with the target. A removed app's history is kept in trash and restored with it.
pier statusshows, per target, the running deploy and anything staged that the nextpier deploywould release.