Skip to main content
A build configuration tells Streampixel how to produce a build from your connected source: which branch or stream, which build type, and what kicks the build off. Set one up once and reuse it on every commit. A project can have several — for example, a Development build on every push to develop plus a nightly Shipping build from main. Find them on your project’s Builds page under Build History → Build configurations, and click New configuration.

Configuration fields

Perforce stream rules

The stream picker shows your depot’s stream tree with each stream’s type. Two types need care:
  • Virtual streams can’t be selected — they’re filtered views, not buildable source.
  • Task streams work, but they’re temporary; the configuration breaks when the stream is removed.

Triggers

Nothing runs automatically. Start a build with the Run button on the configuration’s row whenever you want one.
Any configuration can also be run manually with Run, whatever its trigger.

Auto-deploy

With Auto-deploy on, a successful build is deployed automatically: it enters your project’s deployment pipeline and goes live once processed — the same flow as clicking Deploy by hand. Leave it off if you want to inspect or download builds first and deploy selectively.

Edit or delete a configuration

Use the row actions on the Build configurations table. Deleting a configuration doesn’t touch existing builds — they stay in Build History — but nothing new can be triggered from it, and any schedule stops.

Next

Running and monitoring builds

Stages, statuses, live logs, and what to do when a build fails.

Connect your repository

Not connected yet? Start here.