Deployment Issues via GitHub Actions to Azure #152905
Replies: 1 comment
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
I am currently facing issues with our deployment process to Azure via GitHub Actions. The deployment is taking an excessively long time-sometimes more than 5-6 hours. To address this, I have adjusted the timeout to 30 minutes. Although the deployment often appears as successful on our linked Azure account, the GitHub workflow shows the status as "cancelled" or "error."
We would like to streamline the deployment workflow, ensure that the GitHub Actions display the correct deployment status, improve the deployment speed, and have it update accordingly.
Any help would be appreciated.
P.S. Using free Azure app service account and dont have standard or premium subscripts for this so can monitor the resources
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions