Skip to main content

​
View prebuilds

Navigate to your project settings and click the Prebuilds tab. All project members can view prebuilds and their logs. Each prebuild shows:
  • Date & Time — when the prebuild was created.
  • Class — the environment class and runner used.
  • Triggered by / Ran as — the trigger source (push, schedule, or manual) and the user it ran as.
  • Status & Duration — the current phase (pending, running, snapshotting, completed, failed, cancelled) and elapsed time. During snapshotting, a completion percentage is shown when available from the cloud provider.
  • Snapshot Size — the size of the resulting snapshot, shown once the prebuild completes.

​
Configure prebuild settings

In the project Settings tab, the prebuild configuration section lets you:
  • Enable prebuilds — turn prebuilds on or off for the project.
  • Select environment classes — choose which environment classes to prebuild.
  • Schedule — set the daily prebuild time (hour in UTC).
  • Executor — choose who runs prebuilds (yourself or a service account). The executor’s SCM credentials are used to clone the repository.
  • Timeout — set the maximum duration for a prebuild (5 minutes to 2 hours, defaults to 1 hour).
  • JetBrains warmup — pre-install the JetBrains backend and build project indexes during prebuilds so JetBrains editors start faster. See JetBrains warmup for details.

​
View logs

Click the actions menu on a prebuild row and select Logs to see Dev Container lifecycle command output, automation task logs, build progress, and error messages. When troubleshooting failures, check logs for errors, verify required secrets are configured, and confirm commands do not require user interaction.

​
Trigger prebuilds manually

Click the Run Prebuild button in the top right of your project settings to run prebuilds for all selected environment classes. For specific environment classes, use the CLI: 
ona prebuild trigger <project-id> --environment-class-id <class-id>

​
Cancel prebuilds

Cancel a running prebuild from the Prebuilds tab or via CLI: 
ona prebuild cancel <prebuild-id>
Cancelled prebuilds consume resources until cleanup completes.

​
Bulk cancel and delete

Use the checkboxes on the Prebuilds tab to select multiple prebuilds at once, then choose an action from the bulk-action bar:
  • Cancel prebuilds stops any in-progress prebuilds in the selection. Prebuilds that are already completed, failed, or cancelled are skipped.
  • Delete prebuilds removes the selected prebuilds. New environments will not start from them. Existing environments that were created from these prebuilds keep running and are unaffected.
Bulk actions process each prebuild independently. The progress dialog shows per-item success or failure so you can see exactly which prebuilds were skipped or returned an error.

​
CLI commands

# List prebuilds
ona prebuild list --project-id <project-id>

# Get prebuild details
ona prebuild get <prebuild-id>

# Delete a prebuild
ona prebuild delete <prebuild-id>
See the CLI documentation for configuration commands.

​
Troubleshooting

Prebuild fails: Check logs for errors, verify secrets are configured at organization or project level, and confirm commands do not require user interaction. Environment does not use prebuild: Verify a successful prebuild exists for the environment class and is less than 7 days old. Prebuild stuck: Review logs for hanging commands, check timeout settings, or cancel and retry.