microsoft
CLI introspection should have an error code when visualstudio.com repos are encountered
Given that the product group is migrating away from *.visualstudio.com we should display a descriptive error message advocating users to use dev.azure.com/*.
Original Description:
Describe the bug: Introspection tool does not support visualstudio.com repositories
To Reproduce:
Try running init and get/dashboard command and it does not display data correctly when the repositories are not dev.azure.com.
Expected behavior: Should work just like dev.azure.com
Screenshots:
Additional context:
- [ ] Add support to npm package for visualstudio.com repos
Does this require updates to documentation?: No
@andrebriggs If anyone has an old visualstudio.com project, I would like to use it for testing this one, I can't seem to figure out how to create one for testing.
@samiyaakhtar what are the exact steps needed here? Can you add more detail?
@andrebriggs added a quick checkbox, that's all the detail I have so far
After looking into it more deeply, it seems like most visualstudio.com AzDO projects have been converted to dev.azure.com. This may no longer be a high-pri bug and will close it if i can't find a project to test with.
From Azure Devops Team Blog:
URLs will change from abc.visualstudio.com to dev.azure.com/abc. We will support redirects from visualstudio.com URLs so there will not be broken links.
I don't think we should support this feature but instead give a descriptive error message telling the user to use the Azure DevOps address. We can point folks to https://docs.microsoft.com/en-us/azure/devops/release-notes/2018/sep-10-azure-devops-launch#switch-existing-organizations-to-use-the-new-domain-name-url
cc @samiyaakhtar