Skip to content
cross compile dotnet app

cross compile dotnet app #74

Sign in to view logs

cross compile dotnet app

cross compile dotnet app #74

Manually triggered September 26, 2024 15:07
@YOU54FYOU54F
⁠ f6d3b4b
main
Status Success
Total duration 9m 38s
Artifacts 1

build-test-cross.yml

on: workflow_dispatch
build
6m 40s
build
Matrix: test
publish
1m 7s
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
The following actions use a deprecated Node.js version and will be forced to run on node20: gittools/actions/gitversion/[email protected], gittools/actions/gitversion/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
artifact Expired
254 MB