Unreal Cloud DocsPresets
Reusable build configurations — platform, engine version, trigger, and test settings.
A preset is a reusable build configuration. Every build is created from a preset, so a project needs at least one. Create and manage presets from the project's Presets tab.
Settings
Name
A label to identify the preset, e.g. Windows – main or Android nightly.
Platform
The target platform to build for:
| Platform | Status | Notes |
|---|---|---|
| Windows 64-bit | Available | Packaged Windows build |
| Linux | Available | Packaged Linux build |
| Android | Available | Packaged Android build |
| iOS, macOS, consoles | Coming soon | — |
Unreal Engine version
The engine version to build with, chosen from the list of supported versions in the dialog.
Pick the version your project is developed against — mismatched versions typically fail during checkout or compile.
Trigger
Each preset has exactly one trigger:
| Trigger | Builds when | Manual trigger | Options |
|---|---|---|---|
| None | Only on demand from the dashboard | ✓ | — |
| Push | Every push to the selected branch | ✓ | Branch |
| Pull Request | Every PR opened or updated | — | Base-branch filter |
For Pull Request presets, you can restrict builds to PRs targeting a specific base branch; leave it on Any base branch to build all PRs. They only run from GitHub events, since they need a PR for context — Push and None presets can also be triggered manually at any time.
Run tests
When enabled, the project's automation tests run after a successful build, and a test report is attached to the build. The test filter limits which tests run — it's a +-separated list of automation test path prefixes, defaulting to Project.Functional Tests./Game (Blueprint functional tests in your project's Content folder). See Automated tests.
Cancel previous build
Available for Push and Pull Request triggers. When a new build is triggered for the same preset and branch (or PR), any of that preset's builds still in flight are canceled.
Recommended for busy branches — you usually only care about the latest commit, and canceled builds stop consuming compute.
Editing and deleting
Edit a preset from its row menu in the Presets table. Changes apply to future builds only; past builds keep the configuration they ran with. Deleting a preset does not delete its past builds.