Hello
I’m using SonarQube 25.3.0.104237 and Sonar Scanner CLI 7.0.2.4839.
The uriBaseId
is not taken into account when importing a SARIF report containing a rule violation at the issues level specified as
"ruleId": "my rule",
"level": "warning",
"message": {
"text": "my rule description"
},
"locations": [
{
"physicalLocation": {
"artifactLocation": {
"uri": "my_file.adb",
"uriBaseId": "file://C:/my_folder/"
},
"region": {
"startLine": 23,
"startColumn": 17,
"sourceLanguage": "Ada"
}
},
"logicalLocations": [
{ "fullyQualifiedName": "input", "kind": "function" }
]
}
],
The report is imported but no marker about the issue is available at the specified location in the given file.
This is not supported on your side ? If this is the case, will the relative paths to the uriBaseId
supported in the further versions ?