Sonar Scanner CLI 6.0 stand alone Azure DevOps fails, 5.0 works, on self hosted agent behind proxy

SonarQube Cloud
, ,
2

Hey Richard!

I’m pretty sure this has to do with the Scanner CLI v6.0 moving over to using a sonar.scanner.javaOpts analysis parameter instead of a SONAR_SCANNER_OPTS environment variable (although I guess according to the docs you can use SONAR_SCANNER_JAVA_OPTS now). In your logs, it’s clear you’re using SONAR_SCANNER_OPTS to pass proxy information.

  1. I am personally confused by what happened to SONAR_SCANNER_OPTS and if it should still be backwards compatible, and I’m going to follow up on this
  2. You can keep using v5 of the scanner, or migrate to using either the new analysis parameter or environment variable.