TeamCity将PowerShell参数识别为字符串的技术问询

Let's break down how to resolve this issue where your inherited build configurations are interpreting the powershell.args01 parameter as a single string instead of a list of PowerShell arguments.

Common Causes & Solutions #

1. Check Parameter Configuration in the Template #

First, verify how your powershell.args01 parameter is set up in the build configuration template:

• Ensure the parameter isn't configured with unnecessary quotes. If you've wrapped the entire argument list in quotes (e.g., "-Path .\script.ps1 -Verbose"), TeamCity will treat it as one string. Instead, only quote individual arguments that need it (e.g., -Path "C:\My Folder\script.ps1" -Verbose).
• If your TeamCity version supports it, enable the "Allow command line arguments" option for the parameter (found in the parameter's advanced settings) to hint that this value should be parsed as multiple arguments.

2. Adjust PowerShell Step Execution Mode #

The way you're passing arguments in the PowerShell step might be forcing the parameter into a string. Try switching the step's execution mode:

• Instead of using the "Script parameters" field with %powershell.args01%, switch to running PowerShell via the command line directly. For example:

  powershell.exe -File .\your-target-script.ps1 %powershell.args01%
  

  This tells TeamCity to split the parameter value into separate arguments when invoking PowerShell, rather than passing the entire value as a single string.

3. Validate Inherited Configuration Overrides #

Double-check the three build configurations that inherit the template:

• Make sure none of them have overridden powershell.args01 with a value that adds extra quotes or escapes. Even a single misplaced quote in an inherited parameter can cause the entire list to be treated as a string.
• Confirm that the parameter value in each inherited config matches the format you intended (e.g., space-separated arguments, no wrapping quotes).

4. Test Parameter Parsing with a Debug Step #

Add a temporary command-line build step to your template to debug how TeamCity is handling the parameter:

echo %powershell.args01%

Run a build and check the logs. If the output shows the argument list wrapped in quotes (e.g., " -Path .\script.ps1 -Verbose"), you know the parameter is being treated as a string. Use this to pinpoint where the extra quoting is being introduced.

内容的提问来源于stack exchange，提问作者Dimskiy