I have a simple Function App that I implemented in the Azure Portal.It's up and running fine.
Since I would like to further develop using VS I downloaded the sources, and have setup CI/CD using VSTS. Now when I make changes in VS and commit this, it successfully triggers a build and deploys.
When I check the Azure portal I do see the deployments. No errors anywhere.
Only problem is the changes don't seem to be deployed because whenever I run the function I get same old output. I also downloaded the app content from the portal and checked the sources - still old ones.
So I'm really confused as to what got deployed and where and why is it not showing up. I did restart the app several times to no avail.
Any suggestions?
Related
I am trying to use Azure DevOps pipelines to build a .NET 5 (Core) web app and deploy it to my Azure app service. I can't find any complete examples in the documentation that achieve this so I'm following this:
https://github.com/shahedc/NetLearnerApp/blob/main/azure-pipelines.yml.txt
However, the Azure deploy task keeps returning this vague error:
In my Azure portal I only get this error:
I am assuming the issue is in my pipeline because deployment works when I deploy it directly from the Deployment Center in the Azure portal. Here are the details for the 3 relevant tasks my pipeline:
I found the solution. It turns out the issue was not in the pipeline, but was caused by a Git connection to the app service I had previously set up in the Azure Deployment Center. Even though I disconnected/removed this Git connection, there was somehow still a residual file left over in Azure that was causing the error. I deleted the 'deployments' folder in Kudu (pictured below) and the pipeline started working as expected.
Getting to the above pictured view:
Navigate to your Azure Function project
Search for Advanced Tools
Open PowerShell
Check if you have disk space available.
Yesterday we started getting this error, even if we tried to re-deploy packages that were successfully deployed just an hour before. Our system guys checked and found out that we reached the space limit and that it was time to upgrade.
P.S. I know that this was answered a long time ago. I am just sharing the solution that was not mentioned here and that worked for us.
think what Dan Beaulieu said in above answers is correct, but one thing to add, in my case, after deleting the deployments folder, remember to restart the app service/web app, which will make it take effect.
So I have a web app that has an Angular frontend and a Node.js backend. I'm trying to deploy to Azure using the Azure App Extension in Visual Studio Code. However, this is my first time using Azure so I don't really know what I should do. Right now I have two web apps, one for the frontend and one for the backend, and they are using the same App Service Plan and Resource Group.
When I try deploying the backend, it won't even deploy it. I've tried changing the folder its being deployed from, using the KUDU console to zip deploy, but nothing works.
I tried a tutorial to make a test project and upload that to Azure (as shown here https://learn.microsoft.com/en-us/azure/javascript/tutorial-vscode-azure-app-service-node-01?tabs=bash). That test project deployed perfectly fine to Azure, however, when I went back to try my source code, the folders wouldn't deploy. How do i fix this problem?
Edit: After doing some troubleshooting, I'm getting these error messages:
Cleaning up temp folders from previous zip deployments and extracting pushed zip file D:\local\Temp\zipdeploy\oplaw3rp.zip (178.92 MB) to D:\local\Temp\zipdeploy\extracted
There is not enough space on the disk.\r\n
Looks like you're running out of disk space before the zip fully extracts. Upgrade to Basic or Standard SKU (10 GB of storage) see if that fixes it.
App Service Plans compared -
https://azure.microsoft.com/en-us/pricing/details/app-service/plans/
I'm trying Azure App Services. I've set up a build pipeline in Azure DevOps which builds and pushes my image to Docker Hub and then publishes docker-compose.yml as an artifact.
My release pipeline takes the docker-compose.yml and feeds it to the "Azure Web App for Container" task which succeeds. But the bot goes down and doesn't get back up after the deployment unless I access http://<myappname>.azurewebsites.net, then it starts and is of the latest pushed version. So everything seems to work, except the "restart" or docker-compose up.
I've been reading that I want to add a WebJob to my app service, but since I am using a Linux host I cannot seem to configure this. I've tried adding a curl task after deployment, but this probably executes too early.
Any ideas on how I would get to solve this last piece of the puzzle to have a simple CI/CD environment?
Currently there is zero out of the box support for hosting WebJobs in a Linux hosted app service. I've heard there's a hacky way of doing it (I'll have to find the post) but since it's not supported out of the gate, there's no guarantee it'll work.
Two weeks ago I created 2 App Services, one is a Function App and the other is a PHP website... after having them created, I went to Deployment Center and configured this option to pull the code from an Azure GIT Repo and build & deploy the code using Kudu, everything was working as expected, whenever I made a code change and pushed it, Kudu was taking the latest commit, building and deploying the latest version...
Yesterday it stopped getting the latest commits from the Repo and by the time I tried to re-configure the setup to see if that helps it won't event display the commits anymore.
Here some screenshots showing the Web App and it's continuous deployment setup mapped to the Azure GIT Repo:
WebApp Continuous Deployment Setup
Azure Repo
Does anyone have faced this issue before? What could be potentially causing this situation? Could any quota limit be causing it?
NOTE: I have a Pay-as-you-go subscription.
I'm pretty sure i am doing something wrong.
But let me attempt to explain my situation...
I created an Azure App Service with Continuous Delivery configured. So far i see that all my deployments are successful. When i go to my app service URL i see Service Unavailable.
Now i suspect my problem could be related to what is being deployed.
Note that I am using Visual Studio Online for my source control and build system.
The source/repo only has 3 folders:
- A folder called .vscode
- A folder called Tools (a bunch of .net console apps)
- A folder called Service (my node.js based service)
Now, the source builds successfully.
And the continuous deployment, triggered after a queued build, completes successfully.
But when i go to the service url i see the dreaded message "Service Unavailable".
I suspect the problem is related to this:
Basically im not sure what is being deployed here.
What i want to deploy is just the Service folder (my node.js app).
I suspect somehow that the entire source tree is being deployed.
Some additional details:
Http Protocol: HTTPS
Error: 503 - Service Temporarily Unavailable
Any help/insights are much appreciated!
Updates
I am confused if the Continuous Delivery option can deploy the node.js app. I did come across this article which shows how to deploy node.js app via "Push to Azure from Git".
Updates 2
I'm not entirely sure right now because i havent tried this out. But the answer to this question seems to hold the key (it seems like it is exactly what im looking for).
Updated 3
I was able actually get the node.js app to start. The issue was that the .js file is two folders deep (in the Service folder). I updated the "Startup command" setting under the "Deploy Azure App Service" (under Continuous Delivery build definition). Now i can see (from the Kudu Docker logs) that it is running.
The problem im having now is that the node.js app can't seem to conenct to the Azure SQL database (this works when i run locally).