Issue with Remote 'origin' already exists.

User on forum reported that this issue. Talking to @ahmelsayed, it seemed to happen to others as well. It happened on and off. Our call did remove before adding. It was unlikely race condition in our codes given deployment lock. Looking at LibGit2Sharp did not reveal much clue.

I suggest to fix by checking if the remote exists and has the same refspec. If so, no need to remove and add remote (avoiding this code path in the first place). This should be the main scenario.

Remote 'origin' already exists.
   at LibGit2Sharp.Core.Ensure.HandleError(Int32 result)
   at LibGit2Sharp.Core.Proxy.git_remote_create_with_fetchspec(RepositorySafeHandle repo, String name, String url, String refspec)
   at LibGit2Sharp.RemoteCollection.Add(String name, String url, String fetchRefSpec)
   at Kudu.Core.SourceControl.Git.LibGit2SharpRepository.FetchWithoutConflict(String remoteUrl, String branchName)
   at Kudu.Services.ServiceHookHandlers.ServiceHookHandlerBase.Fetch(IRepository repository, DeploymentInfo deploymentInfo, String targetBranch, ILogger logger, ITracer tracer)
   at Kudu.Services.FetchHandler.<PerformDeployment>d__12.MoveNext()

[davidebbo]

@skapatech looks like libgit2sharp issue is still active. Can you try setting a SCM_USE_LIBGIT2SHARP_REPOSITORY=0 app setting and check if that takes care of it?

[davidebbo]

The linked libgit2sharp issue did not get traction unfortunately.