Skip to content

Add or update the Azure App Service build and deployment workflow config #4

Add or update the Azure App Service build and deployment workflow config

Add or update the Azure App Service build and deployment workflow config #4

Triggered via push April 10, 2026 20:08
Status Failure
Total duration 1m 2s
Artifacts
build-and-deploy
57s
build-and-deploy
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 11 warnings
build-and-deploy
Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
build-and-deploy
Run the command below to authenticate interactively; additional arguments may be added as needed: az logout az login
build-and-deploy
AADSTS700016: Application with identifier '***' was not found in the directory 'xenhey.com'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant. Trace ID: 208d0b7e-f44b-4f7f-a0a0-de89746f3500 Correlation ID: b3c20cb5-aa79-42a9-9742-bbc5313243fb Timestamp: 2026-04-10 20:09:25Z
build-and-deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v1, azure/login@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-deploy: message.cs#L14
The type name 'message' only contains lower-cased ascii characters. Such names may become reserved for the language.
build-and-deploy: reports.cs#L15
The type name 'reports' only contains lower-cased ascii characters. Such names may become reserved for the language.
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: DBScript/College.Designer.cs#L42
'DataSet.DataSet(SerializationInfo, StreamingContext, bool)' is obsolete: 'This API supports obsolete formatter-based serialization. It should not be called or extended by application code.' (https://aka.ms/dotnet-warnings/SYSLIB0051)
build-and-deploy: pages.cs#L15
The type name 'pages' only contains lower-cased ascii characters. Such names may become reserved for the language.
build-and-deploy: encode.cs#L14
The type name 'encode' only contains lower-cased ascii characters. Such names may become reserved for the language.
build-and-deploy: message.cs#L14
The type name 'message' only contains lower-cased ascii characters. Such names may become reserved for the language.
build-and-deploy: reports.cs#L15
The type name 'reports' only contains lower-cased ascii characters. Such names may become reserved for the language.
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.