Skip to content
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.

Deployment from External Git with Bicep Template fails #3312

Closed
Pietervanhove opened this issue Jun 29, 2021 · 3 comments
Closed

Deployment from External Git with Bicep Template fails #3312

Pietervanhove opened this issue Jun 29, 2021 · 3 comments

Comments

@Pietervanhove
Copy link

Hi,

Since last week, we noticed that our deployment of our Web App service is failing, which was working before.
I have created a Bicep Template file to deploy the App Service plan and the App Service. (see attachment)
The web site that I want to deploy is stored on my GitHub Repository, as you can see in the sourcecontrols section.
In the config section, I have configured an application setting "PROJECT", which points to the project file that is stored on my GitHub repository.

When I try to deploy my Bicep Template, the Deployment Center gets configured with my external Git Repository. However, I noticed that the PROJECT property is not created anymore. This causes a failure of the deployment with reason "Unable to determine which solution file to build." This is normal, because the PROJECT property is missing.

When I remove the App Service again, but I don't disconnect my External GitHub, and redeploy, it succeeds because the PROJECT property is configured.

So it seems when my GitHub repository is not connected yet to the deployment center, it is failing...

The Web App name is called eaeaedemoapp.

WebApp.txt
Screenshot 2021-06-29 103346

@suwatch
Copy link
Member

suwatch commented Jun 29, 2021

It could be the limitation in App Settings api where it is async in nature (meaning may take time upto 10s to propagate to the VM even after the api returns successfully). Try to put a delay (say 10s) (not sure if possible - not familiar with this bicep template) between the app settings and source control step and see it that helps or confirms it was an issue.

@Pietervanhove
Copy link
Author

Pietervanhove commented Jun 30, 2021 via email

@jvano
Copy link
Member

jvano commented Apr 29, 2024

Hi

If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

This way we can better track and assist you on this case

Thanks,

Joaquin Vano
Azure App Service

@jvano jvano closed this as completed Apr 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants