Automatic deployment not working with Github repo

Question

Hello,

Here we are trying to support auto deployment for our roosterjs repo so that it can generate a deploy link to our Demo Site, when a pull request is pushed.

I tried to set up this with Azure pipeline by creating an app service in my personal Azure account and configured the deployment so that it is linked to the GitHub repo that I forked from the main repo. Here is the action it created for us. After I pushed a change, I was able to see that it started the job to build and deploy the code. Please see this job where everything looked okay but the deploy link (http://roosterjsbiwu.azurewebsites.net) that was generated doesn't get routed, so it is not working.

Instead, I figured out that the change was actually deployed to https://roosterjsbiwu.scm.azurewebsites.net/, under path /home/site/wwwroot/dist/deploy, so if I go to https://roosterjsbiwu.scm.azurewebsites.net/wwwroot/dist/deploy, I am able to see the demo site shown up, but that link seems only accessible to myself, but not public, and https://roosterjsbiwu.azurewebsites.net/wwwroot/dist/deploy is still not working.

I think there is something that I must have configured wrong. Can I get some help from you to set up this pipeline, or is there another way to do this, Thanks!

Answer 1

Thanks for reaching here! It looks like Container crash. This can happen at two times.

1. At container startup : When we start your container, we'll wait a while for it to start and initialize. We consider the startup to be successful once the container is running and once we get a response from it to a Platform generated HTTP ping so that we know it's ready to respond to HTTP traffic. We'll wait 230 seconds for that to happen. If we don't have a successful start within 230 seconds, we'll assume there's a problem and we'll stop the container.
   2. During runtime: Your app container was running but due to an unhandled exception it exited unexpectedly.

As per findings your app started but did not respond to health checks. This means that our App Service infrastructure has tried pinging the container every second until it responds, indicating that the HTTP server is up.

Could you please configure that, add an app setting called WEBSITES_CONTAINER_START_TIME_LIMIT and set it to the number of seconds you would like for us to wait for your container to start (up to a maximum of 1800) as shown in the image below.

Also suggest viewing the Application Logs to see if there was any exception or error message indicating the possible cause.

Please review the following article that might help you customize and configure your Web App to your requirements https://learn.microsoft.com/en-us/azure/app-service/containers/configure-language-nodejs

Check this article link might be helpful: https://learn.microsoft.com/en-us/archive/blogs/waws/things-you-should-know-web-apps-and-linux#general-information

Let us know if further query or issue remains.