-
Notifications
You must be signed in to change notification settings - Fork 189
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Dashboard baseline project name and version are not set (#1710)
* Fix DashboardBaselineProvider The automatic detection of project name and version introduced in #1663 broke the DashboardBaselineProvider because the project name would not be set and thus the report would be sent to an invalid URL: `/api/reports//version` This commit addresses this issue by setting the project name and version on the StrykerOptions rather than on the DashboardClient and DashboardReporter (like it was originally done in #1532). * Fix uploading the report 1. Unlike `GetFromJsonAsync`, `PutAsJsonAsync` does not ensure a success status code so we call it to make sure the request was successful. 2. The description field of a mutant can not be null else we get an HTTP 400 error with this description: > Invalid report. data.files['IndentationSettings.cs'].mutants[0].description should be string * Fix NullReferenceException in InitialisationProcessTests * Don't try to read project name and project version if not required This should fix the integration error on Azure Pipelines: > Failed to retrieve the RepositoryUrl from the AssemblyMetadataAttribute of /home/vsts/work/1/s/integrationtest/TargetProjects/TargetProject/bin/Debug/netcoreapp3.0/TargetProject.dll Co-authored-by: Rouke Broersma <mobrockers@gmail.com>
- Loading branch information
1 parent
8f90d76
commit e2523e4
Showing
9 changed files
with
69 additions
and
50 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters