Running and monitoring builds

Every build triggered from a build configuration appears under Build History → Recent builds, newest first, with its platform, status, branch, and commit. Click a build to open its detail page: stage-by-stage progress, live logs, and the deploy/download actions.

​

Build statuses

If the configuration has notifications on, the project owner is emailed on success and/or failure — the failure email includes the failed stage and a link to the logs.

​

Build stages

A build moves through six stages, shown as tiles on the detail page:

​

Live logs

The detail page streams build output live — the same output you’d see packaging locally. You can filter by level (Info / Warn / Error), search, toggle auto-scroll, and Copy all. Once the build finishes, Download log saves the full log file.

​

When a build fails

The failed stage is highlighted, and the error is in the logs — cloud builds surface the same errors Unreal would give you locally (compile errors, cook failures, missing plugins). Filter the logs to Error, fix in your repo, push or hit Run again.

​

After the build: deploy or download

A Ready build offers two actions:

​

Deploy for streaming

Deploy creates a deployment — the build enters the same processing pipeline as a manually uploaded .zip and, once activated, replaces your current live deployment across your project’s region. Current sessions aren’t interrupted; new sessions get the new build once distribution completes. From there, everything on Builds applies: statuses, rollback, tagging. If the build was already deployed, the button becomes View deployment.

​

Download the artifact

Download artifact gives you the packaged .zip — the same thing you’d get out of a local BuildCookRun. Use it to ship the build outside Streampixel, archive it, or test it on your own machines.

​

Next