PowerShell

Version

List of PowerShell versions, supported by TeamCity. Since 8.1 is passed to powershell.exe as -Version command line argument

Powershell run mode

Select the desired execution mode on a x64 machine.

Error Output

Specify, how error output is handled by the runner:

• error: any output to stderr is handled as error

• warning: default setting; any output to stderr is handled as warning

  tip

  To fail a build if "an error message is logged by build runner" (see Build Failure Conditions), change the default setting of the Error Output selector from warning to error.

Working directory

Specify the path to the Build Working Directory.

Script

Select whether you want to enter the script right in TeamCity, or specify path to a script:

• Script file: Enter path to Powershell file. It has to be relative to checkout directory.

• Script source: Enter PowerShell script source. Note, that TeamCity references (build parameters and TeamCity system properties) will be replaced in the code.

Script execution mode

Specify the PowerShell script execution mode. By default, Powershell may not allow execution of arbitrary .ps1 files. TeamCity will try to supply the -ExecutionPolicy ByPass argument. If you've selected Execute .ps1 script from external file, your script should be signed or you should make PowerShell allow execution of arbitrary .ps1 files. If the execution policy doesn't allow running your scripts, select Put script into PowerShell stdin mode to avoid this issue.

Script arguments

Available if "Script execution mode" option is set to "Execute .ps1 script with the -File argument". Specify here arguments to be passed into PowerShell script.

tip

There is a known issue with Powershell using the -File that causes the wrong exit code to be returned to TeamCity. For details, refer to TW-21554 and TW-34410.

Additional command line parameters

Specify parameters to be passed to powershell.exe.