Forces the build step (and likely the job) to fail if any dangerous character is detected in any variable value. This is the safest option.
This option can result in builds failing despite Windows Batch build steps not even using the potentially unsafe variables. To prevent that, combine this global option with the option Only Keep Specified Environment Variables of individual build steps. This way, only environment variables the build step actually needs would be passed to it, and unsafe values in any others would not cause the build step to fail.
Replaces each environment variable value identified as unsafe with the value REDACTED
.
This prevents command execution via environment variables, but it can result in unexpected behavior in scripts making use of affected environment variables.
Print a warning about the presence of unsafe environment variable values to the build and system logs.
This provides no protection from unsafe environment variable values being used in Windows Batch build steps, but helps you understand the impact of enabling a safer option.