- We deploy a Function to Azure FunctionApp, using Octopus - Deploy an Azure Web App - as per https://octopus.com/blog/azure-functions
a. Function Deploys ok.
b. Trigger function
c. Function Host is restarted with references to Assembly reference changes detected.
2019-01-09T00:23:58.706 [Info,ProcessStudyResultForGateway] Assembly reference changes detected. Restarting host…
2019-01-09T00:23:58.706 [Info] Environment shutdown has been triggered. Stopping host and signaling shutdown.
2019-01-09T00:23:59.487 [Info] Job host stopped
-
We deploy a Function to Azure FunctionApp, using Visual Studio Publish
a. Function Deploys ok.
b. Trigger function
c. Function Host does not restart and functions run as expected. -
We deploy a Function to Azure FunctionApp, using Octopus, once again.
a. Function Deploys ok.
b. Trigger function
c. Function Host does not restart and functions run as expected.
As such, it seems Visual Studio is performing some type of MS magic, to optimize the code, and decide on how to resolve some assembly dependencies.
We know we have a Dependency Hell situation, but unfortunately, we’re not in a position to resolve that right now, (indeed, its actually difficult to see exactly what needs to be resolved, as the Microsoft logging of what its detecting as being in conflict leaves a lot to be desired. that is, there is no logging.)
We have a very unique architecture - Azure function invokes a Legacy executable! which we’re also migrating to a dll, but tbh, I don’t foresee this resolving the issue, rather potentially more likely to exacerbate it.
We have a support case open with Microsoft, but aren’t making any headway there.
I cannot find many examples of this online, nor any relating specifically to Octopus deploys.
Is this something that you’ve seen in the past with Octopus deployments?
Is there any plans to support MSDeploy type deployments, (or do you perceive this as how functions are currently deployed, using the Web App Deployment task?)
I know this task was never designed to deploy functions, but some enterprising soul discovered it could, and is now the official approach.
We deploy other functions using this task, and it works well for those. Just missing that little bit of VS magic for this one!
Thanks for reading, hope to hear back.
Mark Van Cooten
Release Engineer,
Volpara Solutions.