Checkout mlops-project-template@cindy-test to s/mlops-project-template
Closed this issue · 3 comments
Describe the bug or the issue that you are facing
Is it correct to use a branch different to main?
Starting: Checkout mlops-project-template@cindy-test to s/mlops-project-template
Steps/Code to Reproduce
Same as https://github.com/Azure/mlops-v2/blob/main/documentation/deployguides/deployguide_ado.md
Section: Set up source repository with Azure DevOps
Expected Output
I dont have an error per see, but its weird to me that its using a named branch (cindy-test) instead of main.
Versions
I am using: initialise-project.yml
from mlops-v2 repo
Which platform are you using for deploying your infrastrucutre?
Azure DevOps (ADO)
If you mentioned Others, please mention which platformm are you using?
No response
What are you using for deploying your infrastrucutre?
Pre-Deployed
Are you using Azure ML CLI v2 or Azure ML Python SDK v2
Azure ML Python SDK v2
Describe the example that you are trying to run?
I am just following the section:
Setup MLOps V2 and a New MLOps Project in Azure DevOps
from:
https://github.com/Azure/mlops-v2/blob/main/documentation/deployguides/deployguide_ado.md
We use ADO not GHA
looks like when I imported the repos, the default branches are not the main ones
@levalencia just experienced same issue, so after running step to init the mlopsv2demo repo I never got the python sdk v2 sub-folders, as cindy-test was the default branch being picked up by the pipeline. Had to go change default branch of repo to main.
Same for mlops-v2 repo here on next run, which shows branch feathr as default (and main as failed, with further beautifully named main_xxx branches).
I imagine a fix to take the default from github into ADO (i.e. main), or enhancing the step-by-step guide would be best @setuc ?