# Build options

Source: https://hashisoft.com/docs/dashboard/build/introduction

Control build output

Configure diagnostics, verification and optional post-build tasks. The build report records the transformations applied and any methods the engine skips.

## Configuration

These entries belong in the `engine` block of your RR configuration.

```rr
engine ^ {
  writeDiagnostics true;
  skipVerify false;
  smokeRun false;
}
```

## Local and remote builds

The remote Java worker enables bytecode verification and disables smoke runs and output signing. Local builds use the settings supported by your engine distribution.

## Option reference

For options beginning with `skip`, `false` enables the pass.

### Build reports

boolean

`writeDiagnostics`

Writes transformation counts, skipped sites and failure details to the build report.

Panel default `true`

### Verify bytecode

boolean

`skipVerify`

Controls bytecode verification. Keep verification enabled. Application behavior still requires runtime testing.

Panel default `false`

### Smoke test

boolean

`smokeRun`

Runs the output application as a smoke test. Requires an entry point and dependencies. Remote builds always disable this option.

Panel default `false`

### Sign output

boolean

`signOutput`

Requests output signing. Signing material must be provided separately. Remote builds disable signing.

Panel default `false`

### Time budget in seconds

number

`buildTimeBudgetSeconds`

Sets the engine time budget in seconds. Remote builds enforce a separate processing limit.

Panel default `900`Range `1–86400`

## Related guides

[RR configurations ](https://hashisoft.com/docs/configurations)[Submit a build ](https://hashisoft.com/docs/quickstart)