Skip to content
cross compile dotnet app

cross compile dotnet app #34

Sign in to view logs

cross compile dotnet app

cross compile dotnet app #34

Manually triggered May 23, 2024 15:39
@YOU54FYOU54F
⁠ 7504ae8
main
Status Success
Total duration 10m 37s
Artifacts 1

build-test-cross.yml

on: workflow_dispatch
build
6m 57s
build
Matrix: test
publish
30s
publish
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 9 warnings
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
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.
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.
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.
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.
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.
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.
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.
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.
publish
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: gittools/actions/gitversion/[email protected], gittools/actions/gitversion/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Artifacts

Produced during runtime
Name Size
artifact Expired
253 MB