You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified this is the correct repository for opening this issue.
I have verified no other issues exist related to my problem.
I have verified this is not an issue for a specific package.
I have verified this issue is not security related.
I confirm I am using official, and not unofficial, or modified, Chocolatey products.
What You Are Seeing?
When running a build that includes both SonarQube and Dependency-Check task, SonarQube does not find the reports generated by Dependency-Check. It appears that the path is relative and at some point in the build the working directory changes such that the relative path to these reports changes.
For example, with the relative path of ./code_drop/DependencyCheckReports the following output is found when the Finalise-SonarQube task runs:
What is Expected?
That the Dependency-Check reports are generated and the Finalise-SonarQube task is able to collect and upload them.
How Did You Get This To Happen?
Run the build, with SonarQube environment variables set:
Checklist
What You Are Seeing?
When running a build that includes both SonarQube and Dependency-Check task, SonarQube does not find the reports generated by Dependency-Check. It appears that the path is relative and at some point in the build the working directory changes such that the relative path to these reports changes.
For example, with the relative path of
./code_drop/DependencyCheckReports
the following output is found when theFinalise-SonarQube
task runs:What is Expected?
That the Dependency-Check reports are generated and the
Finalise-SonarQube
task is able to collect and upload them.How Did You Get This To Happen?
Run the build, with SonarQube environment variables set:
System Details
N/A
Installed Packages
Output Log
Additional Context
Related to #110
The text was updated successfully, but these errors were encountered: