Page tree

Skip to end of metadata
Go to start of metadata

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.

analysis_typeOutputs a comma separated list of enabled analysis types (e.g., Static, Generation and Execution)${analysis_type}
env_varOutputs the value of the environmental variable specified after the colon. ${env_var:HOME}
config_nameOutputs the name of executed Test Configuration.${config_name}
dtp_projectOutputs the name of DTP project specified in the settings file using dtp.project option.${dtp_project}
project_moduleOutputs 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_nameOutputs the name of the host.${host_name}
user_nameOutputs the name of the current user.${user_name}
osOutputs the name of the operating system.${os}
archOutputs the name of the operating system architecture${arch}
exec_envOutputs information about the execution environment. By default, this variable outputs a combination of the ${os} and ${arch} variables. It can be customized by configuring the exec.env option in the .properties file (see Report Settings).${exec_env}
scontrol_branchOutputs 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_nameOutputs the name of the tool (i.e., Jtest, C++test, dotTEST).${tool_name}
jvm_propOutputs the value of the Java vm property specified after the colon.${}

  • No labels