SebastianSchuetze
commented
2 years ago Thanks for the report @hvl71 it checked it and it is per se not a bug with the cmdlet, but implemented incomplete in regards to the API.
Also documenting it for myself here. So, I had the following setup:
- repo with a
mainand adevbranch - an azure pipeline exists pointing to a yaml file in the dev branch
- yaml file does not exist on main
- I run the cmdlet
Following error I get:
PS F:\repos\general_github\vsteam> Set-VSTeamDefaultProject -Project 'YAML Tests'
PS F:\repos\general_github\vsteam> Test-VSTeamYamlPipeline -PipelineId 41
WARNING: An error occurred while loading the YAML build pipeline. File /azure-pipelines.yml not found in repository https://dev.azure.com/razorspoint-test/YAML%20Tests/_git/YAML%20Tests branch refs/heads/main version 96e7436b59b550a411dc5f6c7dc42f7a5f8416bb.Warning is different but comes down to the same problem.
When calling the following API endpoint: https://docs.microsoft.com/en-us/rest/api/azure/devops/pipelines/preview/preview?view=azure-devops-rest-6.1
You can give the pipeline Id. If you don't specify anything else, it tries to do the test against the branch which is named "main" of the repo. Additionally, I tried to switch the default branch to dev and then run it. It still didn't work.
- Then I also deleted the
mainbranch and then I got your message. - The cmdlet is not setting any default branch here.
- The AzDO API is in the backend setting it to an expected default branch, which is in your and my case
main. - It's independent if this branch exists. That also means that the API is not even checking what the default branch in the repo is
How to resolve it?
- It is a bug in the API in your case (if you only have a
devbranch and that is the default one) so I will report it so they may be able to fix it (e.g. take the current default branch if nothing is given) - Will add a Parameter
Branchto the cmdlet which creates aresourcesJSON object in the body like described in the API. Checked it even how the GUI does it when trying to do a validation:
and it sends an object like the following which is mostly empty and always seems to have only one resource in it:
{
"resources": {
"pipelines": {},
"repositories": {
"self": {
"refName": "dev"
}
},
"builds": {},
"containers": {},
"packages": {}
},
"templateParameters": {},
"previewRun": true,
"yamlOverride": "YAML Code here"
}
Hi
We encounter an issue when trying to validate a yaml pipeline using the Test-VSTeamYamlPipeline cmdlet.
We run:
Result:
We see the behaviour on both versions we have tried (7.2.0 and 7.4.0)
We have observed that our PipelineId only has pipeline runs on our development branch. We have never run the pipeline on our master branch (we don't have a main branch).
If we validate the yaml agains another PipelineId which has had a pipeline run against the relevant master branch, the yaml validates fine.
Steps to reproduce Validate a known valid yaml pipeline against a PipelineId that have no pipeline runs on master or main in Azure Devops Service
Expected behavior Yaml validates without errors or fails with more clear error message about reason
Actual behavior:
Environment data: Windows 10 Server: Azure DevOps Service