We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test-VSTeamYamlPipeline -PipelineId 21 -FilePath '.\azure-pipelines.yml' -Branch 'feature/coverage' -ProjectName 'XXXXX'
The job would run without error and the Branch parameter was supported based on examples in the documentation for this function.
Test-VSTeamYamlPipeline : A parameter cannot be found that matches parameter name 'Branch'. At line:1 char:74 + ... line -PipelineId 21 -FilePath '.\azure-pipelines.yml' -Branch 'featur ... + ~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Test-VSTeamYamlPipeline], ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Test-VSTeamYamlPipeline
Windows
Azure DevOps Services
No response
Billing : 5.1-preview.1 Build : 5.1 Core : 5.1 DistributedTask : 6.0-preview DistributedTaskReleased : 5.1 ExtensionsManagement : 6.0-preview Git : 5.1 Graph : 6.0-preview HierarchyQuery : 5.1-preview MemberEntitlementManagement : 6.0-preview Packaging : 6.0-preview Pipelines : 5.1-preview Policy : 5.1 Processes : 6.0-preview Release : 5.1 ServiceEndpoints : 5.0-preview TaskGroups : 6.0-preview Tfvc : 5.1 VariableGroups : 5.1-preview.1 Version : VSTS
Name Value ---- ----- PSVersion 5.1.19041.1682 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.19041.1682 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
The text was updated successfully, but these errors were encountered:
Thanks. Do you feel confident in giving it a go to fix it? Otherwise we can do it at some point.
Sorry, something went wrong.
I think I might be capable although I need to dive into it, but the hard part is finding time to do so. Won't mind if you beat me to it ;-)
No branches or pull requests
Steps to reproduce
Expected behavior
The job would run without error and the Branch parameter was supported based on examples in the documentation for this function.
Actual behavior?
On Which OS have you tried it?
Windows
What was your server version?
Azure DevOps Services
Other server version
No response
Log output of used API
Log output of $PSVersionTable
The text was updated successfully, but these errors were encountered: