Page Comparison

WS_ACTIVATION_KEY

Your generated activation key in the WhiteSource application

V

X

X

bolt.op.activation.key

21.6.3

WS_CONFIG_ACCOUNT_NAME

The account name that will hold the global whitesouce-config repository.

Default: “whitesource-config”

V

X

X

X

21.6.3

WS_CONFIG_REPO_NAME

The repository name of the global configuration repository.

Default: “whitesource-config”

V

X

X

X

21.6.3

WS_HTTPS_CERT_FILE_PATH

If using a certificate file - path to the certificate file

V

X

X

X

21.6.3

WS_HTTPS_KEY_FILE_PATH

If using a certificate file - path to the private key file

V

X

X

X

21.6.3

WS_KEYSTORE_FILE_PATH

If using a Java keystore - path to the keystore file.

V

X

X

X

21.6.3

WS_KEYSTORE_PASSWORD

If using a Java keystore - password for the keystore file

V

X

X

X

21.6.3

WS_CREATE_ISSUES

The ability to globally enable/disable Issues creation across all of your organization's repositories.

Default: true 

V

X

X

bolt4scm.create.issues

21.6.3

WS_CREATE_CHECK_RUNS

The ability to globally enable/disable build statuses across all of your organization's repositories. 

Default: true 

V

X

X

bolt4scm.create.check.runs

21.6.3

WS_REMEDIATE_WEBHOOK_URL

The destination of the Remediate network endpoint to intercept webhooks.

Default: http://remediate-server:8080/webhook

V

X

X

webhook.remediate.url

Must include the “/webhook” suffix

21.6.3

UNIFIED_AGENT_PRINGPRINT_LOGS

If set to true the UA logs will also be printed to the stdout, like the scanner logs.

X

V

X

X

The UA logs can be very long.

21.6.3

SCM_SCANNER_LOG_DIRECTORY 

Configure the path to both the scanner and the UA log files. Using this property will also append a partial request token to the log filenames.

X

V

X

X

21.6.3