The documentation for the azure devops yaml integration is very scant.
One of the examples includes:
inputs: SonarQube: 'YourSonarqubeServerEndpoint' scannerMode: 'CLI' configMode: 'manual' cliProjectKey: 'YourProjectKey' extraProperties: "sonar.cfamily.build-wrapper-output=bw_output"
But I cannot find a complete list of what input parameters can be used.
In our pipelines we have:
SonarCloud: 'my_connection' organization: 'my_own' scannerMode: 'CLI' configMode: 'manual' cliProjectKey: 'my_project_key' cliProjectName: 'my_project_name' cliSources: '.' extraProperties: | sonar.cfamily.cache.enabled=false sonar.cfamily.build-wrapper-output=foobar/bw-output sonar.cfamily.gcov.reportsPath=foobar/gcovReports sonar.cfamily.cppunit.reportsPath=foobar/cppunit sonar.coverageReportPaths=foobar/coverageSonar.xml sonar.verbose=true
The sonar extra properties map to the -D options we would specify on the command line but what for example is “cliSources” ?
I would like to see at least a table of the available options for example.
For context. Here is a current problem I am having.
The paths in foobar/coverageSonar.xml assume the analysis is being run with foobar as the working directory. For bash tasks I can set the working directory as:
- task: Bash@3 displayName: Do something with coverage inputs: targetType: inline workingDirectory: foobar
Is there an equivalent for the sonarCloudPrepare task?
Currently I have to alter the paths in the coverage report to be relative to the source root rather than foobar or sonar will ignore them but perhaps I can just change the working directory instead somehow?
A similar request is Documentation Update - Azure DevOps Integration