Continuous Deployment from GitHub to Azure (ASP.NET 5 and MVC 6)

Question

I have problems with Continuous Deployment from GitHub to Azure. I have a general price level, and the problem disappears if I go to the basic price level. This is for an ASP.NET MVC 6 (RC1) application.

Essentially, I get the following error: http://pastebin.com/PgARgurg

The bit that is allocated:

Restore failed There is not enough space on the disk. 

If I publish directly from Visual Studio to a generic level, it works great. This is only when using continuous deployment where it falls.

Any ideas?

Answer 1

Shared instances have very limited resources, especially in terms of disk size. The integration of continuous deployment from GitHub involves bringing a copy of the code to disk with each change, and this is not always cleared immediately (or in general). Direct publishing to Azure from Visual Studio automatically clears previous deployment packages. The reason why upgrading your level solves the problem is the allocated and increased available disk space. You should upgrade to Basic if you decide that continuous integration (and therefore disk space) is important to your work.

Answer 2

There is one more warning. Instances of shared web applications have a 300 Mb limit on the Temp Folder .

The asp.net 5 RC1 app uses more Temp Folder storage than the Beta8 app. Currently, it’s almost impossible to deploy RC1 through continuous integration into the free application service.

Answer 3

Basically, the recovered packet size does NOT match the published application packages.
You can understand why this happens by opening the restored packages ... For example, in the scenario below, the published package has only the necessary content to run the application.

Restored JSON.NET Package Contents:

Published JSON.NET Package Content:

Perhaps you should publish the application from your continuous deployment?