Skip to content

Build and deploy dotnet core app to Azure Function App - async-job-gb-app #9

Build and deploy dotnet core app to Azure Function App - async-job-gb-app

Build and deploy dotnet core app to Azure Function App - async-job-gb-app #9

Manually triggered May 17, 2025 15:40
Status Failure
Total duration 5m 52s
Artifacts

main_async-job-gb-app.yml

on: workflow_dispatch
build-and-deploy
5m 43s
build-and-deploy
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 4 warnings
build-and-deploy
Deployment Failed!
build-and-deploy
Error: Failed to deploy web package to App Service. Internal Server Error (CODE: 500) at Kudu.<anonymous> (D:\a\_actions\Azure\functions-action\v1\lib\appservice-rest\Kudu\azure-app-kudu-service.js:238:41) at Generator.next (<anonymous>) at fulfilled (D:\a\_actions\Azure\functions-action\v1\lib\appservice-rest\Kudu\azure-app-kudu-service.js:5:58) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
build-and-deploy
Failed to deploy web package to App Service. Internal Server Error (CODE: 500)
build-and-deploy
When request Azure resource at PublishContent, zipDeploy : Failed to use D:\a\_temp\temp_web_package_32945019346256044.zip as ZipDeploy content
build-and-deploy
Execution Exception (state: PublishContent) (step: Invocation)
build-and-deploy
Failed to deploy web package to App Service.
build-and-deploy: AsyncJob.cs#L82
Possible null reference return.
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: AsyncJob.cs#L82
Possible null reference return.
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.