Hi, Erik
Try using the 'removeAdditionalFileFlag', by default the deployment won't delete older files:
removeAdditionalFilesFlag: true
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have an Umbraco CMS Web App hosted on Azure from a GitHub repo since last year. Nothing big, small blog, shared plan.
Trying to deploy some new small changes and ran into this problem. My quota seems fine, and I've never seen this before. Any suggestions?
Huge thanks for any help,
/Erik
Hi, Erik
Try using the 'removeAdditionalFileFlag', by default the deployment won't delete older files:
removeAdditionalFilesFlag: true
Looks like this atm:
# Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy
# More GitHub Actions for Azure: https://github.com/Azure/actions
name: Build and deploy ASP.Net Core app to Azure Web App - nausea87-xxx
on:
push:
branches:
- main
workflow_dispatch:
jobs:
build:
runs-on: windows-latest
steps:
- uses: actions/checkout@v4
- name: Set up .NET Core
uses: actions/setup-dotnet@v1
with:
dotnet-version: '8.x'
include-prerelease: true
- name: Build with dotnet
run: dotnet build --configuration Release
- name: dotnet publish
run: dotnet publish -c Release --property:PublishDir=${{env.DOTNET_ROOT}}/myapp
- name: Upload artifact for deployment job
uses: actions/upload-artifact@v3
with:
name: .net-app
path: ${{env.DOTNET_ROOT}}/myapp
deploy:
runs-on: windows-latest
needs: build
environment:
name: 'Production'
url: ${{ steps.deploy-to-webapp.outputs.webapp-url }}
steps:
- name: Download artifact from build job
uses: actions/download-artifact@v3
with:
name: .net-app
- name: Deploy to Azure Web App
id: deploy-to-webapp
uses: azure/webapps-deploy@v2
with:
app-name: 'nausea87-umbracoweb'
slot-name: 'Production'
publish-profile: ${{ secrets.AZUREAPPSERVICE_PUBLISHPROFILE_xxx }}
package: .
I am guessing somewhere under deploy?
I solved this now after finding the Console :) I removed the zipdeploy folder under c/local/temp and re-run the jobs. Seemed to work.
Thanks for the help Luke!
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more