Deploy & build logs

Two streams, two questions

The deploy log narrates the pipeline itself, one line per stage: cloning, validating the manifest, building, starting the new container, waiting for health, promoting it - or the exact reason it failed. It answers "what happened to my deploy."

The build log carries only the raw docker build stdout and stderr - dependency resolution, every layer, every warning - untouched by the platform. It answers "why did the build itself fail."

Both stream live over their own connection while a deploy is in progress, and both close together the moment the deploy finishes, whether it succeeded or failed.

Persisted by plan

Once a deploy finishes, both logs are written to object storage in full. How long they stay depends on your plan - long enough on every tier to debug a deploy that failed overnight without needing the browser tab that was open when it happened. After that window they're deleted, not merely hidden.

What doesn't end up in either

Secret values are scrubbed from every line before it's published or persisted - see secrets for exactly what counts as a secret versus a plain env var that's shown in the clear.