We currently use Perforce as our SCM for SonarQube/SonarScanner. When running on the command line on Windows, blame detection works perfectly and the results reflect on the dashboard. However, when we use it on Linux with our automation scripts, it suddenly fails.
Here's an example of the quirk I've found. Below is the command based on the output of debug logs:
Windows (OK):
p4 annotate -c -i -db C://SampleFile.js#have
Linux (FAILS)
p4 annotate -c -i -db //SampleFile.js#have
Result: - file(s) not on client
Good day!
We currently use Perforce as our SCM for SonarQube/SonarScanner. When running on the command line on Windows, blame detection works perfectly and the results reflect on the dashboard. However, when we use it on Linux with our automation scripts, it suddenly fails.
Here's an example of the quirk I've found. Below is the command based on the output of debug logs:
Windows (OK): p4 annotate -c -i -db C://SampleFile.js#have
Linux (FAILS) p4 annotate -c -i -db //SampleFile.js#have
Result: - file(s) not on client
Linux (OK) p4 annotate -c -i -db //SampleFile.js
Thanks!