Every build setting has exactly one trigger. The trigger decides when the build fires.Documentation Index
Fetch the complete documentation index at: https://buildpixel.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Manual
The simplest. A user clicks Build now in the dashboard, or you call the API:Push
The build setting fires every time a push to the tracked branch (or stream) lands.GitHub
GitHub pushes are delivered via the BuildPixel App’s webhook automatically — no setup in your repo needed. Set:main → matching build settings fire.
Perforce triggers
Perforce has no native webhook. Wire a Helixchange-commit trigger script that calls BuildPixel’s trigger endpoint on every submit:
p4 triggers:
Scheduled
Pick a schedule for the build (e.g. nightly at 2am UTC). At fire time, BuildPixel pulls the latest commit / changelist and builds. Settrigger: "scheduled" and configure the schedule in the dashboard’s build setting view.
Useful for nightlies, weekly snapshots, or coordinating with other systems.
Trigger metadata
Every build records its trigger:- Manual via dashboard:
triggeredBy: "user:<userId>" - Manual via API:
triggeredBy: "api_token:<tokenId>" - Push:
triggeredBy: "push:<commit>" - Schedule:
triggeredBy: "cron"