You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 19, 2024. It is now read-only.
I am using sample_yaml_builds/dotnet-windows.yml as a template for building and publishing an azure function project in Azure DevOps. I am not building and deploying in the same step, rather I intend to publish the zip file as a build artifact and deploy from a separate pipeline.
I have both pipelines (build and deploy) set up, and they both run successfully, however I am unable to see my functions through azure portal after deployment. The portal does show that a package has been deployed and even correctly indiactes the build from which it is deployed. However the functions are not available.
I examined my build artifact and compared that to the results of publishing to a folder from Visual Studio and found that the build artifact zip contained an additional root folder (with the same name as my solution file) that then contained the published outputs; the results of publishing to a folder from VS did not contain this additional directory layer.
I modified my build file, setting modifyOutputPath: false for the DotNetCoreCLI task, and this result was then consistent with VS publish. The new artifact deployed successfully to Azure with expected results.
I am submitting this issue for repro with the suggestion that modifyOutputPath be set to false if generated build artifacts do not deploy as expected
I am using sample_yaml_builds/dotnet-windows.yml as a template for building and publishing an azure function project in Azure DevOps. I am not building and deploying in the same step, rather I intend to publish the zip file as a build artifact and deploy from a separate pipeline.
I have both pipelines (build and deploy) set up, and they both run successfully, however I am unable to see my functions through azure portal after deployment. The portal does show that a package has been deployed and even correctly indiactes the build from which it is deployed. However the functions are not available.
I examined my build artifact and compared that to the results of publishing to a folder from Visual Studio and found that the build artifact zip contained an additional root folder (with the same name as my solution file) that then contained the published outputs; the results of publishing to a folder from VS did not contain this additional directory layer.
I modified my build file, setting modifyOutputPath: false for the DotNetCoreCLI task, and this result was then consistent with VS publish. The new artifact deployed successfully to Azure with expected results.
I am submitting this issue for repro with the suggestion that modifyOutputPath be set to false if generated build artifacts do not deploy as expected