Skip to content

Deploy DotNet project to Azure Function App dev #8

Deploy DotNet project to Azure Function App dev

Deploy DotNet project to Azure Function App dev #8

Manually triggered August 29, 2024 15:09
Status Success
Total duration 2m 2s
Artifacts

deploy-dev.yaml

on: workflow_dispatch
build-and-deploy
1m 50s
build-and-deploy
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build-and-deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build-and-deploy
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
build-and-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build-and-deploy
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.