3 ms·
Azure Pipelines is just slow. I'm not sure even how to fix it. Checkout stage of our code from Azure Repos easily count for half a minute. Npm install goes for
by AlfeG 5y ago
Azure Pipelines is just slow. I'm not sure even how to fix it.
Checkout stage of our code from Azure Repos easily count for half a minute. Npm install goes for a 1.5 minute with npm cache hit. Total build times are around 20 minutes...
- dachryn 5y agothere is an undocumented feature, called zip deploy, if you deploy to an app service. Give it a go, it might just work. I use it to deploy a Python Django website. You need to add a setting in your App Service environment variables. It took me an escalation from our account manager, to get a good support guy, who informed me of this functionality. Here is the summary of my support ticket: WEBSITE_RUN_FROM_PACKAGE” and value as 1. We performed deployment and it took around 30 secs. We also verified that the app is working fine. Now you will do some changes and deploy once more to verify end to end pipeline. Zip deployment is a feature of Azure App Service that lets you deploy your function app project to the wwwroot directory. The project is packaged as a .zip deployment file. The same APIs can be used to deploy your package to the d:\home\data\SitePackages folder. With the WEBSITE_RUN_FROM_PACKAGE app setting value of 1, the zip deployment APIs copy your package to the d:\home\data\SitePackages folder instead of extracting the files to d:\home\site\wwwroot. It also creates the packagename.txt file. After a restart, the package is mounted to wwwroot as a read-only filesystem. Article for reference: https://docs.microsoft.com/en-us/azure/azure-functions/run-functions-from-deployment-package#integration-with-zip-deployment https://docs.microsoft.com/en-us/azure/azure-functions/run-f...