Umbraco Logs fails deployment
s
Is there anyway, when using Releases through Azure to prevent the log files from tripping it up?
m
Why is the deployment deploying that file? Or at least thats how the error reads 🙂
We deploy to a slot so there is nothing running then swap it over once we have checked it then stop the staging slot again
So no downtime and no locked file issues
j
☝️this. If slots aren't an option, and you're already trying to do a shutdown or use app_offline then check you've got nothing going on in your app that's preventing it from gracefully shutting down.
k
Don't deploy temporary files. Forgot to
.gitignore
?
s
There is no temporary files there, it is on
app_offline
too. No options for slot as cheap env
k
Are you sure the publish operation isn't trying to replace that log file? It looks like it. Why else would it try to touch it? Or is the publish operation deleting non-package files?
m
Is the log file committed into your repo? Or any references to it in the csproj file? Web App deployment task should ignore it by default.
s
Nope, it's 100% not commited. 😦
m
Are you willing to share your csproj file?
s
Do you have the option enabled to delete existing files on the server? That might be the issue that causes this error. Ideally, Web Deploy should skip the umbraco/logs directory so you don't lose your logs after each deploy. This answer on StackOverflow might help you: https://stackoverflow.com/a/60781168/135007
k
I asked this too above but didn't get an answer. We use this option but it doesn't fail our deploys even if temporary files are not removable, so maybe the web deploy is configured in an unusual way.
17 Views