All of my builds started failing today with a new version of AzureRM App Service deploy version 2.1.3.
I use Hosted pool for Team Services (Windows).
2016-11-11T13:02:36.2644641Z ##[section]Starting: Deploy AzureRM App Service: xxx
2016-11-11T13:02:36.2744703Z ==============================================================================
2016-11-11T13:02:36.2744703Z Task : Azure App Service Deploy
2016-11-11T13:02:36.2744703Z Description : Update Azure App Service using Web Deploy / Kudu REST APIs
2016-11-11T13:02:36.2744703Z Version : 2.1.3
2016-11-11T13:02:36.2744703Z Author : Microsoft Corporation
2016-11-11T13:02:36.2744703Z Help : [More Information](https://aka.ms/azurermwebdeployreadme)
2016-11-11T13:02:36.2744703Z ==============================================================================
2016-11-11T13:02:36.3044674Z ##[error]File not found: 'C:\a\_tasks\AzureRmWebAppDeploy_xxx\2.1.3\azurermwebappdeployment.js'
2016-11-11T13:02:36.3074644Z ##[section]Finishing: Deploy AzureRM App Service: xxx
Yesterday deployments worked correctly (version 2.0.7).
Any ideas what could be causing this and how to fix it?
Meanwhile I can use work-around: deploy with Azure App Service: Classic which is newly tagged as Deprecated (and much much slower).
Thank you in advance for any help.
Issue is now fixed according to https://github.com/Microsoft/vsts-tasks/issues/3074 and my tests.
I have a hacky solution which may or may not work but can be tried. Go to the BD/RD where this task is getting used. Change anything and capture the save BD/RD call using the network tab in Chrome. See the request JSON, there you will have versionSpec field for the AzureRMWebApp which will be set to 2.1.3 or *.
Replay the call using some REST client like POSTMAN and set the versionSpec to 2.1.2 or whichever version was working for you. This can be done only through APIs. And don't change anything from UI since it will again put the latest version in the JSON.
I would advise to use POSTMAN + POSTMAN Interceptor chrome addons for this since it makes capturing and replaying calls very easy and also allows you to change the request JSON.
It seems the build agent has silently upgraded the AzureRmWebAppDeploy task to 2.1.4 and it works again. I don't know if it is because I recreated the deploy step in the release configuration or not.
Related
I deployed the official material-ui ssr example to Microsoft Azure, it doesn't work. I also deployed it to Heroku, it still doesn't work. On my local machine and on codesandbox , everything looks good. I don't know what I'm missing.
UPDATE
You can choose docker when you create webapp services. I think it will help you solve the issue.
PRIVIOUS
I think this project has some bug in it.
You can raise a support on azure portal, or submit a issue on github.
I have try to use many ways to deploy ssr project.
Continuous deployment to Azure App Service [Failed]
FTP, then run start command. [Failed]
Use VSCode to publish. [Failed]
Paste zip file into kudu. [Failed]
After all the attempts, I guess that a certain command of the project may take up a lot of resources, so this project has potential bugs, and the azure team can assist in finding the cause of the deployment failure.
This is my error msg.
I'm trying to deploy a Laravel + Vue app over an Azure App Service - Web App. It is however very unclear and I cannot find any proper solution inside Microsoft's documentation to get it into working.
'Traditional' deployment workflow
What I typically do to deploy my code (outside CI/CD):
sync Git repository
run composer install
run npm run prod (which is a shorthand for compiling webpack in my case)
Done
There is a really easy approach with a Docker container, where in my Dockerfile I just configure php-apache image with additionally installed Nodejs (w. NPM).
However I would like to find a solution to use Azure's built-in features to configure this deployment. Is it possible?
I can use Windows or Linux Web Apps. No difference for me.
I recommend that you use continuous deployment. For specific operations, you can check the official documentation.
Recommended reason:
As long as it runs successfully locally and continuously deploys through git, the project can be released, and later updates only need to submit code through git.
You can easily view the deployment log in Action in git.
Simple operation and convenient update
Steps:
First, ensure that the project is running normally locally, and create web app services on the portal. (Linux is recommended for the nodejs program, which can avoid many problems caused by dependencies)
According to the official document, in the Deployment Center, select github for release
Check the release information of Action on the official github website and wait for the release to be completed
Note:
If it is a nodejs program or other language program, if the Linux operating system is used, the Startup Command may need to be configured in the Configuration. If the program cannot be accessed normally after release, then try to set npx serve -s (nodejs program, other Language program), and then proceed to restart the webapp.
I've created two pipelines: build and release for Nodejs app.
Here is the link to nodejs app repo: azure web service
Here is the tasks for build pipeline:
Here is the wwwroot folder structure:
So it is look like all required files are present.
Despite that, I'm constantly receiving:
You do not have permission to view this directory or page
I've tried to add web.config file, but it did not help.
I have front end application on same App service Plan and it works, so it is no way that I have bad service plan.
Do you have any suggestions?
Thanks a lot.
I was able to deploy my service only after using nodejs-docs-hello-world starter.
It is looks like web.config is a required file, btw, still did not find any meaningfull documentation for web.config.
Make sure your azure nodejs env support your js syntax (import from ...), in other case use webpack or typescript.
I'have found App Service Editor very helpful if you want to debug your code errors. See section Output.
I had a problem also with nodejs version, despite the fact I choosed node 12 tls during web app creation, I have noticed that my app used node 6 under the hood. So I changed default nodejs version to 10. See here how to do it
Also, I want to thank #Jason Pan for his help.
I am just trying to upgrade my Azure Mobile Service(AMS) to Mobile app service with the help of documentation link provided here.
I have successfully migrated my Mobile service with the help of button provided on portal. After that I also installed node server on my local machine and installed following node package -
npm i -g azure-mobile-apps-compatibility
I have also obtained my Azure Mobile Service script files. Following is my folder hierarchy of Scripts folder -
Now here in this step I am stuck. I am trying to Scaffold the new Azure Mobile Apps backend with the help of following Node command -
scaffold-mobile-app scripts out
When I executed above command, I am getting following errors in node command prompt -
After looking at the errors I thought that there is some problem with my municipality api files. So I also tried removing my municipality.js and permissions.js file. After that I re executed the scaffolding command. But it again gave me the following error -
I did some research to resolve this error. But I did not get any relevant help in that context. Can someone help/ guide me so that I can proceed further in this upgrade activity?
I really want to use dotnet core and azure. I used the amazing yeoman aspnet generator to scaffold out a basic app. This ran fine locally using Kestrel.
I then added the app to my github account and linked this to a new Azure Web App instance to deploy the thing. But no joy :( I get a 500 error.
Looking at the setting of the webapp it saying using .net framework 4.6 is that right or am I missing something, cannot see an option for .net core 1.0 that I expected to see??
I tried turning on logging in the setting with detailed exceptions etc but have not found anything to give me a clue as to what going on.
#Andy, Could you try access into kudu site(yoursite.scm.azurewebsites.net) and start web.cmd file in this folder (/home/site/approot)? I suggest you can try to start this command. Meanwhile, please refer to Shawn's blog 'https://wildermuth.com/2016/04/29/Deploying-ASP-NET-Core-RC1-to-Azure-App-Services '. Any information or update, please let me know.