Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Unable to fork DevOps git repo - service not supported

Tags:

git

fork

devops

I am trying to fork a DevOps git repo and I repeatedly get this error:

TF400860: The current version of the following service is not supported: GitOdb. Version: 1700, MinVersion: 1700.

Fork Error

This exact operation worked for me last week. Any ideas why it isn't working now?

like image 467
Kirk Liemohn Avatar asked May 20 '20 14:05

Kirk Liemohn


People also ask

How do I enable repositories on Azure DevOps?

On your Azure DevOps project page, select Project settings at lower left, and then select Repositories in the left navigation. On the Settings tab of the All Repositories page, set Default branch name for new repositories to On, and then enter a default branch name.

How do I clone a repository from github to Azure DevOps?

From your web browser, open the team project for your Azure DevOps organization, and then choose Repos > Files to open the Files view. In the Files view, choose Clone to launch the Clone Repository popup. Copy the clone URL from the Clone Repository popup.

How do I migrate from github to Azure DevOps?

Import into a new repoSelect Repos, Files. From the repo drop-down, select Import repository. If the source repo is publicly available, just enter the clone URL of the source repository and a name for your new Git repository.


Video Answer


3 Answers

It seems there is some service degradation. It's probably just a matter of time until it starts working again. You can follow this problem in the Developer Community. There is also the status page for azure devops.

like image 185
Duarte Silva Avatar answered Oct 17 '22 14:10

Duarte Silva


There is a service disruption on Microsoft side on Repos and Pipelines in the United States. Microsoft seems to be on top of it, and as of writing this comment, it's been 29 minutes. They'll fix it sometime soon, so we just have to sit and wait.

Duarte Silva provided some good links for the status page for Azure DevOps

like image 2
kipras Avatar answered Oct 17 '22 14:10

kipras


Here is the comment from Azure Dev Ops.

The issue is now fully mitigated with the completed rollback. This was caused by a unique intersection of updates over the past two days that didn't follow our normal compatibility constraints. We will be addressing that before the next deployment and have a repair item to identify solutions to prevent future occurrences of this. We apologize for the impact this had on our customers.

For More: https://status.dev.azure.com/_event/188823884

like image 1
Arshath Shameer Avatar answered Oct 17 '22 14:10

Arshath Shameer