Thank you for the message.
We are using a setup where pipeline checkouts two different repositories under the build agents source folder (E:\agent_work\7\s). First one is our templates repo that contains all centrally maintained azure pipeline templates. Second is the actual source code repo that we want to analyze.
We have about 40 of those source repos and most of them have their SonarCloud issues analyzed and reviewed thru version 2 of SonarCloud devops tasks. The root of the analysis is something like E:\agent_work\7\s\reponame for all pipelines so changes in the paths are difficult since all issues will be reported as new issues if the paths don’t match after version 3 upgrade.
I ran the pipeline system.debug on.
There is the log for the SonarCloudAnalyze@3
470ce5ad-1256-4578-9854-30e6580d6958__apis_build_builds_80943_logs_27.log (22.5 KB)
For the SonarCloudPrepare@3 the task does not log much
470ce5ad-1256-4578-9854-30e6580d6958__apis_build_builds_80943_logs_13.log (1.0 KB)