Workaround for APIScan build parameter. (#7382)

* Switch to test branch.

* Switch back to master.

build/buildpipeline/security/DotNet-CLI-Security-Windows.json

@@ -259,6 +259,29 @@
         "failOnStandardError": "true"
       }
     },
+    {
+      "environment": {},
+      "enabled": true,
+      "continueOnError": false,
+      "alwaysRun": false,
+      "displayName": "Workaround for long package Id",
+      "timeoutInMinutes": 0,
+      "condition": "succeeded()",
+      "refName": "PowerShell24",
+      "task": {
+        "id": "e213ff0f-5d5c-4791-802d-52ea3e7be1f1",
+        "versionSpec": "1.*",
+        "definitionType": "task"
+      },
+      "inputs": {
+        "scriptType": "inlineScript",
+        "scriptName": "",
+        "arguments": "-packageId $(CliLatestPackageId)",
+        "workingFolder": "",
+        "inlineScript": "param($packageId)\n\nif ($packageId.Length -ge 16)\n{\n    Write-Host \"Build number for security build is the package Id. TSA has a limit of 16 characters for build number. Since package Id is greater than 16 characters, build number will be set to current date time in yyyymmddHHMMss format.\"\n    $CliLatestPackageId = Get-Date -Format yyyymmddHHMMss\n    Write-Host \"##vso[task.setvariable variable=CliLatestPackageId;]$CliLatestPackageId\"\n}",
+        "failOnStandardError": "true"
+      }
+    },
     {
       "enabled": true,
       "continueOnError": true,