Failed to set up deployment source for web app

Question

I'm having a problem setting up a deployment source on an Azure Web App for my Visual Studio Team Services account.

I had just reorganised my solution - added a new project and changed the root directory of my git repo to be the parent folder of the old root folder (I used to have my solution & project in the same folder, which was my git root, but now I have .\solution\ & .\solution\project1 & .\solution\project2, with .\solution now being my git root).

Continuous deployment had been setup via my Visual Studio Team Services account, and was working fine, but after this reorganisation it stopped working. I tried deleting and recreating the Azure Web Site, and also re-created the VS Team Services project, but that made no difference.

When I attempt to set the Deployment Source for my Web App in the portal, it fails with the following error:

Failed to set up deployment source for web app my-web-app(Staging), 
using Visual Studio Team Services. Repository 'UpdateSiteSourceControl' 
operation failed with System.InvalidOperationException: Vso GetRepository: 
Cannot find repository 
https://my_account.visualstudio.com/DefaultCollection/_git/my_repo_name
at 
Microsoft.Web.Hosting.SourceControls.VsoProxy.<GetRepository>d__3f.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Web.Hosting.Administration.VsoSiteRepositoryProvider.<UpdateSiteSourceControl>d__6.MoveNext().

Also, can you check whether you're still able to deploy with a solution that doesn't have your recent change? That would help identify whether that's really the cause, vs some unrelated Azure/VSTS issue. — David Ebbo
Yes @david, I tried it again with a single project solution and it worked fine. The problem seems to be with multi-project solutions. As I mentioned in a comment below yesterday, there is a workaround using a custom deployment script when using the classic portal, using the new portal it looks like it may be possible to get it working by using an ARM template (see github.com/Azure/azure-content/blob/master/articles/…), but I've not tried this yet. — David Grogan

Cece Dong - MSFT Cece Dong - MSFT · Accepted Answer · 2016-04-20T09:34:11

Instead of setting the Deployment Source in the new portal. You can try to set up deployment from source control on Dashboard:

Failed to set up deployment source for web app

1 Answers