Skip to content

Build and deploy ASP.Net Core app to Azure Web App - app-umbraco-multisite #103

Build and deploy ASP.Net Core app to Azure Web App - app-umbraco-multisite

Build and deploy ASP.Net Core app to Azure Web App - app-umbraco-multisite #103

Manually triggered November 19, 2024 15:30
Status Success
Total duration 5m 44s
Artifacts 1
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, Azure/appservice-settings@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, actions/checkout@v2, actions/setup-dotnet@v1, Azure/appservice-settings@v1, azure/CLI@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build
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.

Artifacts

Produced during runtime
Name Size
.net-app
169 MB