(#127)(ENGTASKS-3098) Use absolute paths for Dependency-Check generated reports #128
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description Of Changes
The PR uses the MakeAbsolute method to ensure that the absolute path is used by SonarQube for the HTML and JSON reports generated by Dependency-Check.
Motivation and Context
These paths are specified in the
Initialise-SonarQube
task prior to the reports being generated, then the working directory changes before theFinalise-SonarQube
task runs. The result is that the SonarQube upload looks in the wrong path when it is time to upload the reports.By using the absolute path for these reports, the change in working directory does not affect the report upload.
Testing
.\build.bat --verbosity=diagnostic --target=CI --testExecutionType=none --shouldRunAnalyze=false --shouldRunIlMerge=false --shouldObfuscateOutputAssemblies=false --shouldRunChocolatey=false --shouldRunNuGet=false --shouldRunSonarQube=true --shouldRunDependencyCheck=true
Operating Systems Testing
N/A
Change Types Made
Change Checklist
Related Issue
Fixes #127
Task ENGTASKS-3098