powershell - TFS 2015.3定制构建步骤未将变量发送到脚本

Question

我一直严格遵循发现here，here和here的设计指南，但是我不断收到此PowerShell错误:

Cannot process command because of one or more missing mandatory parameters: SourcePath FilePattern BuildRegex.

相关的配置数据如下。

我已经检查并再次检查以确保变量存在于我的task.json文件中。我还查看了其他工作任务(例如VSBuild)的配置，变量声明和PowerShell执行语法没有显着差异。

这里可能出什么问题了？这是一个非常简单的体系结构，没有什么可打破的。但是，显然已经做到了这一点。

从task.json:

"inputs": [
  {
    "name": "SourcePath",
    "type": "filePath",
    "label": "Source path",
    "defaultValue": "",
    "required": true,
    "helpMarkDown": "Path in which to search for version files (like AssemblyInfo.* files). NOTE: this is case sensitive for non-Windows systems." 
  },
  {
    "name": "FilePattern",
    "type": "string",
    "label": "File pattern",
    "defaultValue": "AssemblyInfo.*",
    "required": true,
    "helpMarkDown": "File filter to replace version info. The version number pattern should exist somewhere in the file(s). Supports minimatch. NOTE: this is casese sensitive for non-Windows systems."
  },
  {
    "name": "BuildRegEx",
    "type": "string",
    "label": "Build RegEx pattern",
    "defaultValue": "\\d+\\.\\d+\\.\\d+\\.\\d+",
    "required": true,
    "helpMarkDown": "Regular Expression to extract version from build number. This is also the default replace RegEx (unless otherwise specified in Advanced settings)."
  },
  {
    "name": "BuildRegExIndex",
    "type": "string",
    "label": "Build RegEx group index",
    "defaultValue": "0",
    "required": false,
    "helpMarkDown": "Index of the group in the Build RegEx that you want to use as the version number. Leave as 0 if you have no groups.",
    "groupName": "advanced"
  },
  {
    "name": "ReplaceRegEx",
    "type": "string",
    "label": "RegEx replace pattern",
    "defaultValue": "",
    "required": false,
    "helpMarkDown": "RegEx to replace with in files. Leave blank to use the Build RegEx Pattern.",
    "groupName": "advanced"
  },
  {
    "name": "ReplacePrefix",
    "type": "string",
    "label": "Prefix for replacements",
    "defaultValue": "",
    "required": false,
    "helpMarkDown": "Prefix for the RegEx result string.",
    "groupName": "advanced"
  },
  {
    "name": "ReplaceSuffix",
    "type": "string",
    "label": "Suffix for replacements",
    "defaultValue": "",
    "required": false,
    "helpMarkDown": "Suffix for the RegEx result string.",
    "groupName": "advanced"
  },
  {
    "name": "FailIfNoMatchFound",
    "type": "boolean",
    "label": "Fail if no target match found",
    "defaultValue": "false",
    "required": false,
    "helpMarkDown": "Fail the build if no match is found for the replace RegEx in the target file(s).",
    "groupName": "advanced"
  }
],
"execution": {
  "PowerShell3": {
    "target": "VersionAssembly.ps1"
  }
}

从VersionAssembly.ps1:

[CmdletBinding()]
param(
  [string][Parameter(Mandatory=$True)][ValidateNotNullOrEmpty()] $SourcePath,
  [string][Parameter(Mandatory=$True)][ValidateNotNullOrEmpty()] $FilePattern,
  [string][Parameter(Mandatory=$True)][ValidateNotNullOrEmpty()] $BuildRegex,
  [string]$BuildRegexIndex,
  [string]$ReplaceRegex,
  [string]$ReplacePrefix,
  [string]$ReplaceSuffix,
  [string]$FailIfNoMatchFound,
  [string]$BuildNumber = $ENV:BUILD_BUILDNUMBER
)

Answer 1

显然，我的关注程度不够……我错过了this page的警告:

Words of warning

Tasks can be versioned, use this to your advantage. All build definitions use the latest available version of a specific task, you can’t change this behavior from the web interface, so always assume the latest version is being used.

If you don’t change the version number of your task when updating it, the build agents that have previously used your task will not download the newer version because the version number is still the same. This means that if you change the behavior of your task, you should always update the version number!

一旦我弄清了一切，一切就很好了。