Command Reference

This page lists CLI commands and corresponding SBT plugin flags. For general concepts like Build Scanner, Test Listener, Build Session IDs, Test Stages, and Execution Modes.

CLI Commands

java -jar sl-build-scanner.jar -sbt -configfile <config-file> -executionType <executionType> -workspacepath <project-root> 
Command
Parameters
Description

-sbt

none

Generate SBT-specific configuration and wire plugin into project

-configfile

<file>

Path to JSON configuration file (sl-config.json)

-workspacepath

<dir>

Root directory of your SBT project

-restoreSbt

none

Reverts all SBT modifications applied by Build Scanner

-executionType

scanonly / testsonly / disabled

Overrides the execution mode defined in JSON config

-logLevel

info / debug / warn / error

Sets the log verbosity

-help

none

Displays CLI usage information

circle-info

Tip: Paths (-configfile, -workspacepath) can be absolute or relative to the current working directory. Use -restoreSbt to undo any plugin wiring changes.

SBT Plugin Flags Reference

This table shows the SBT plugin flags alongside CLI commands for a quick mapping.

CLI Command / JSON
SBT Plugin Flag
Description

-executionType scanonly

sealightsRunScanOnly := Some(true)

Run only Build Scanner phase, skip tests

-executionType testsonly

sealightsRunTestOnly := Some(true)

Run only Test Listener phase, reuse existing scan

-executionType disabled

sealightsDisabled := Some(true)

Temporarily disable all SeaLights integration

-configfile <file>

slConfigFile := "<file>"

Path to JSON configuration file

-logLevel <level>

sealightsLogLevel := "<level>"

Set log verbosity (info/debug/warn/error)

-workspacepath <dir>

N/A (use working directory)

Root of SBT project; implicitly used by plugin

-restoreSbt

N/A

Restore build.sbt to pre-integration state

Usage Example – Scan Only in SBT

Usage Example – CLI equivalent

Last updated

Was this helpful?