general

--detect.component.location.analysis.enabled=false

If set to true, Detect will save an output file named 'components-with-locations.json' in the Scan subdirectory detailing where in the project's source code OSS components are declared.

All components will be included when using Detect in offline mode. Only policy violating components will be included for Rapid and Stateless Scan modes.

--detect.component.location.analysis.status=false

If set to true, Detect status and exit code will be affected by the status of the Component Location Analysis run.

--detect.blackduck.correlated.scanning.enabled=false

When enabled, Detect activates the Black Duck SCA correlated scanning capability to enhance match accuracy.

The correlated scanning capability must be present and enabled in your Black Duck SCA server before you enable the correlated scanning feature in Detect.

--detect.target.type=SOURCE,IMAGE 

Informs detect of what is being scanned which allows improved user experience when scanning different types of targets.

Changes the behaviour of detect to better suite what is being scanned. For example, when IMAGE is selected and the DOCKER tool applies and has not been excluded, detect will not pick a source directory, will automatically disable the DETECTOR tool and run BINARY/SIGNATURE SCAN on the provided image.

--detect.follow.symbolic.links=true

If set to true, Detect will follow symbolic links when searching for detectors, when searching for files that select detectors (such as Bitbake and Sbt) need, when searching for directories to exclude from signature scan, and when searching for binary scan targets. Symbolic links are not supported for Impact Analysis.

--detect.wait.for.results=false

If set to true, Detect will wait for Black Duck SCA products until results are available or the detect.timeout is exceeded.

Note that scan failures will exit with FAILURE_SCAN (6) and time out will exit with FAILURE_TIMEOUT (2) code.

--detect.ignore.connection.failures=false

If true, Detect will ignore any products (eg. Black Duck SCA) that it cannot connect to.

If true, when Detect attempts to boot a product (eg. Black Duck SCA) it will also check if it can communicate with it - if it cannot, it will not run the product.

--detect.parallel.processors=1

The number of threads to run processes in parallel, defaults to 1, but if you specify less than or equal to 0, the number of processors on the machine will be used.

--detect.force.success=false

If true, Detect will always exit with code 0.

--detect.force.success.on.skip=false

If true, Detect will always exit with code 0 when a scan of any type is skipped. Typically this happens when the Black Duck SCA minimum scan interval timer has not been met.