Skip to content

feat: import-pact-file (v2/v3/v4 http) #40

feat: import-pact-file (v2/v3/v4 http)

feat: import-pact-file (v2/v3/v4 http) #40

Triggered via pull request August 30, 2024 17:49
@YOU54FYOU54F
synchronize #29
feat/pact_files
Status Success
Total duration 7m 52s
Artifacts 1

build-test-cross.yml

on: pull_request
Matrix: test
publish
0s
publish
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 8 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.

Artifacts

Produced during runtime
Name Size
artifact Expired
254 MB