The following table shows variables that can be used in settings values.
We recommend you avoid using spaces, +, /, or any other special characters when setting variables or values for configuration settings, as some API calls may require properly encoded URLs.
| Variable | Description | Example |
|---|---|---|
analysis_type | Outputs a comma separated list of enabled analysis types (e.g., Static, Generation and Execution) | ${analysis_type} |
env_var | Outputs the value of the environmental variable specified after the colon. | ${env_var:HOME} |
config_name | Outputs the name of executed Test Configuration. | ${config_name} |
dtp_project | Outputs the name of DTP project specified in the settings file using dtp.project option. | ${dtp_project} |
project_module | Outputs the name of the tested project's module. If more than one module is provided as an input, the first tested module name is output followed by an ellipsis (...). The variable can be configured in the settings file with the project.module option. | ${module_name} |
host_name | Outputs the name of the host. | ${host_name} |
user_name | Outputs the name of the current user. | ${user_name} |
os | Outputs the name of the operating system. | ${os} |
arch | Outputs the name of the operating system architecture | ${arch} |
exec_env | Outputs the execution environment. Ths variable is a concatenation of ${os} and ${arch} variables. It can be configured in the sittings file with the exec.env option. | ${exec_env} |
scontrol_branch | Outputs the source control branch name for the tested project. If more than one branch name is detected, the first branch name is output followed by an ellipsis (...). The variable can be configured in the settings file with the scontrol.branch option. | ${scontrol_branch} |
tool_name | Outputs the name of the tool (i.e., Jtest, C++test, dotTEST). | ${tool_name} |
jvm_prop | Outputs the value of the Java vm property specified after the colon. | ${jvm_prop:os.name} |
