Scanner error after migrating azure devops task to v2

[Colin]

Hey there!

Do you have SONAR_SCANNER_OPTS set in your build variables to provide more memory to the scanner? If so, in this new version, you’ll need to migrate to the SONAR_SCANNER_JAVA_OPTS variable.

Update Sonar CLI scanner 5.0.1 to 6.1

Yes, this is a bit of a unique one, because SONAR_SCANNER_OPTS is now passed to the process that bootstraps the scanner, while SONAR_SCANNER_JAVA_OPTS gets passed to the scanner itself. So to maintain compatibility for both versions, yes, you’ll need to include both.