Triggering Builds
Start builds manually from the dashboard or automatically from GitHub events.
Builds start in one of two ways: manually from the dashboard, or automatically from GitHub events.
- Open the project's Builds tab and click Trigger build.
- Pick a preset and confirm.
Only presets with a None or Push trigger can be built on demand, because they resolve to a concrete branch. Pull Request presets need an actual PR for context, so they only run from GitHub events.
Manual builds always build the latest commit of the preset's branch.
Once your repository is connected, presets with a Push or Pull Request trigger start builds automatically:
- Push presets build on every push to their configured branch.
- Pull Request presets build the PR's head commit whenever a PR is opened or updated, if the PR's base branch matches the preset (or the preset accepts any base branch).
Each automatic build creates a check run on the commit in GitHub, so build status appears directly on your commits and pull requests. See GitHub integration.
Concurrency and queueing
Your organization has a build concurrency limit set by your plan. Builds beyond the limit queue until a slot frees up.
If you regularly see builds waiting in queued, consider raising concurrency in Billing.
Canceling builds
Cancel a running build from its menu in the Builds table. If a preset has Cancel previous build enabled, newer triggers cancel older in-flight builds of the same preset and branch automatically.