Azure Web App Service not Updating after new push using local git deploy

Question

Azure Web App Service not Updating after new push using local git deploy

Jason Tanuwijaya 0

Hello Microsoft,

So I have deploy an web app service on azure, but it seems like the app is showing the old deployment even though I have push a new version using local git I have check the log it show this Uploaded image but when I look up the /wwwroot it still have the previous deployment (24 April)

User's image

Can you help me of why is this happening? I have try to restart the web app but it still have the same problem

Alekhya Vaddepally 820 Reputation points Microsoft External Staff

2025-04-29T08:54:33.2866667+00:00

HiJason Tanuwijaya,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Jason Tanuwijaya 0 Reputation points

2025-04-29T10:06:52.5466667+00:00

Hello @Alekhya Vaddepally

I'm using Local git for the deployment, there are no such option for me to check this part that you mentioned

You can also check: Manually use the Sink Pretty Arts: Azure Portal> Deployment Center> Sink option.

Go to your web app in Azure portal. Click on SYNC to trigger redevelopment and artifact sinks. Under the Personnel Center> Log, verify whether the publishing phase has succeeded or if there were hidden errors.

Copying file still hasn't updated the web and I also failed to redploy the the wwwroot, the web has an error now.

I will make a new instance of web app and redeploy there. After that I will try to all the configuration properly and see if my future push have the same problem or not.

Thank you for the help,

I will ask for more query if I still have the same problem.

1 answer

Your answer

Alekhya Vaddepally 820 Reputation points Microsoft External Staff

2025-04-29T08:54:33.2866667+00:00

HiJason Tanuwijaya,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Jason Tanuwijaya 0 Reputation points

2025-04-29T10:06:52.5466667+00:00

Hello @Alekhya Vaddepally

I'm using Local git for the deployment, there are no such option for me to check this part that you mentioned

You can also check: Manually use the Sink Pretty Arts: Azure Portal> Deployment Center> Sink option.

Go to your web app in Azure portal. Click on SYNC to trigger redevelopment and artifact sinks. Under the Personnel Center> Log, verify whether the publishing phase has succeeded or if there were hidden errors.

Copying file still hasn't updated the web and I also failed to redploy the the wwwroot, the web has an error now.

I will make a new instance of web app and redeploy there. After that I will try to all the configuration properly and see if my future push have the same problem or not.

Thank you for the help,

I will ask for more query if I still have the same problem.

Answer 1

HiJason Tanuwijaya,

From images you have provided that, Your git -finished log shows that your new commit was successfully pushed (improving API on April 28, 2025).
However, when you inspect the Azure Web app/home/site/wwwroot directory, the files are still from the old deployment (24 April 2025).
This usually occurs because the local git -finance is not automatically extracted on the azure and place the latest build output in /wwwroot /.
Instead, Azure uses a temporary construction directory during the sins (often/TMP) and publishes only after a successful build stage/home/site/wwwroot/only after a successful build phase.
In your case, it seems that the construction of the deployment was successful, but the publication step was not completed properly. Hence the old version remains active.

The most common cause:

Build Artifact (output) was created, but did not copy to / wwwroot / folder.

The deployment script may remember the published phase.

A permitted or storage quota can be a issue.

Sometimes, an Azure Deployment engine bug may be the cause of incomplete publication.

You can also check:
Manually use the Sink Pretty Arts: Azure Portal> Deployment Center> Sink option.

Go to your web app in Azure portal.
Click on SYNC to trigger redevelopment and artifact sinks.
Under the Personnel Center> Log, verify whether the publishing phase has succeeded or if there were hidden errors.
If the sink does not work, you can reopen your changes or use Kudu console:

Visit https://<yourapp>.scm.azurewebsites.net/DebugConsole.
Navigate to the build artifact location and manually copy files into /home/site/wwwroot/.

Ensure that the scm_do_build_during_deployment configuration is set on the correct in the application settings. (This setting ensures proper construction and deployment.)
If everything else fails, you can clearly clear and re -deploy wwwroot. Be very careful with this - backup first.

https://learn.microsoft.com/en-us/azure/app-service/deploy-local-git?tabs=cli#troubleshoot-deployment
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Let me know if you have any further Queries.

Alekhya Vaddepally 820 Reputation points Microsoft External Staff

2025-05-02T08:44:18.2966667+00:00

Hi Jason Tanuwijaya,
If this answer was helpful and pointed you in the right direction, please consider clicking "Accept Answer"—it may benefit other community members reading this thread. If you have any further questions, feel free to let us know.

Share via

Azure Web App Service not Updating after new push using local git deploy

1 answer

Your answer