Thank you for following up on this and sharing more details about the repository and environment. The reason I wanted to understand more about your test scenario and configuration, is because I want to be able to provide better suggestions and advises. If I have the bigger picture, I could be more helpful.
I understand you have GIT repository hosted in AzureDevops and I assume that your Test Studio project is connected to it. So, whenever you schedule a test list with the CommandLineClient, it gets the source control and scheduling settings from that project's Settings.aiis file. As a result the scheduling server tries to pull the latest version of the test list and all of the referenced tests from the repository. If you access the repository with the different credentials from your domain ones, you need to impersonate the scheduling service with the login details of the repository.
That above feature is only working for TFS repositories and the scheduling server can't reach the GIT repository. We have a feature request for that and it is in our backlog for future releases, but I can promise when it will be implemented. What you need to do is, disconnect the Test Studio project from source control and then schedule the test list, using the CommandLineClient. To do that:
- open the project in Test Studio;
- right click on the project name in the Project explorer;
- click on Git Source Control -> Remove Source Control Binding.
I hope the above workaround for Git source controlled projects will help you schedule the test lists with CommandLineClient. I remain available to continue our discussion further, if you need any help or you have additional questions.