> ## Documentation Index
> Fetch the complete documentation index at: https://docs.streampixel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Build configurations

> Define how builds are produced from your connected repository — build type, branch, and triggers.

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

| Field                | Options                  | Notes                                                                                           |
| -------------------- | ------------------------ | ----------------------------------------------------------------------------------------------- |
| Platform             | `win64`                  | More platforms coming soon.                                                                     |
| Build type           | Development, Shipping    | Development builds faster and keeps debug features; Shipping is what you put in front of users. |
| Branch *(GitHub)*    | Any branch               | Picked from your repo's branch list; defaults to `main`.                                        |
| Stream *(Perforce)*  | Any buildable stream     | See stream rules below.                                                                         |
| Trigger              | Manual, Push, Schedule   | See [Triggers](#triggers).                                                                      |
| Notify on completion | On / Off *(default off)* | Emails the project owner when the build succeeds.                                               |
| Notify on failure    | On / Off *(default on)*  | Emails the project owner when the build fails.                                                  |
| Auto-deploy          | On / Off *(default off)* | Sets the new build live on success — see below.                                                 |

### 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

<Tabs>
  <Tab title="Manual">
    Nothing runs automatically. Start a build with the **Run** button on the configuration's row whenever you want one.
  </Tab>

  <Tab title="Push">
    Every push to the configured branch starts a build automatically — commit, and a few minutes later there's a fresh build in Build History. Pair with **Auto-deploy** for a full commit-to-stream pipeline.
  </Tab>

  <Tab title="Schedule">
    Builds run on a recurring schedule — hourly, daily, weekly, or monthly, at the time and timezone you pick. The schedule builder previews the next runs so you can confirm before saving. Typical use: a nightly build from `main` regardless of commit activity.
  </Tab>
</Tabs>

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

<CardGroup cols={2}>
  <Card title="Running and monitoring builds" icon="bars-progress" href="/resources/cloud-builds/running-and-monitoring-builds">
    Stages, statuses, live logs, and what to do when a build fails.
  </Card>

  <Card title="Connect your repository" icon="code-branch" href="/resources/cloud-builds/connect-your-repository">
    Not connected yet? Start here.
  </Card>
</CardGroup>