Web app deployment on Azure fails as GitHub workflow is timed out

Mauro 0 Reputation points
2023-04-21T06:26:35.56+00:00

I've built a dash app and tried to deploy it to Azure Web App Services from Github Actions. I had the app running for a few days, but after some incremental changes, the deployment suddendly failed when making changes. The app still works and it seems that the deployment was successful, but on Github the workflow shows to have failed and timed out after 6 hours. Also on the Azure portal, it shows that the deployment was unsuccessful. Does anyone has experienced this before? I have tried to re-run the workflow and deploy it several times, but the workflow can never finish.

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,007 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. brtrach-MSFT 16,676 Reputation points Microsoft Employee
    2023-04-22T03:28:54.87+00:00

    It sounds like the deployment process is timing out after 6 hours, which is the maximum allowed time for a GitHub Actions workflow. This can happen if the deployment process is taking longer than expected due to a large number of files or slow network speeds. To resolve this issue, you can try optimizing your deployment process to reduce the time it takes to deploy your app. Here are a few suggestions:

    1. Use a smaller deployment package: If your deployment package is too large, it can take a long time to upload to Azure. Try removing any unnecessary files or compressing your files to reduce the size of your deployment package.
    2. Use a faster network connection: If your network connection is slow, it can take a long time to upload your deployment package to Azure. Try using a faster network connection or uploading your deployment package from a different location.
    3. Use a different deployment method: If you are still having issues with the GitHub Actions workflow, you can try deploying your app using a different deployment method, such as Azure DevOps or FTP.
    4. Increase the timeout limit: If none of the above solutions work, you can try increasing the timeout limit for your GitHub Actions workflow. You can do this by adding the following line to your workflow file:
    jobs:
      deploy:
        timeout-minutes: 720 # Increase timeout limit to 12 hours
    
    

    This will increase the timeout limit to 12 hours, which should give your deployment process enough time to complete. I hope this helps! Let me know if you have any further questions.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.