SONARQUBE_SCANNER_PARAMS vs SONAR_SCANNER_JSON_PARAMS

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)

    SonarQube Scanner 2.17.2 (jenkins)

When running sonar-scanner-npm from jenkins we get this warning:

[WARN] Bootstrapper: SONARQUBE_SCANNER_PARAMS is deprecated, please use SONAR_SCANNER_JSON_PARAMS instead 16:19:24

It seems that the plugin is setting the environment variable with the deprecated version of the name. I couldn’t find any issue or post about it and 2.17.2 seems to be the latest version. Am I missing something?

Sonar Community Roundup, October 19 - 25
4

Hi Erik,

Thanks for your feedback. We created a ticket to review the issue.
In the meantime, you can safely ignore the warning.

Regards

1 Like
7

Thanks for the feedback Javier!

8

Same here. Well message is a bit different

[16:22:24.077+01:00] - [WARNING] Property ‘env.SONARQUBE_SCANNER_PARAMS’ is encrypted. The encryption of scanner properties is deprecated and will soon be removed.

1 Like
9

Same issue affecting Valentin Delaye is happening here when this pipeline runs:

withSonarQubeEnv('SonarQubeConf') { 
    sh 'mvn sonar:sonar -Dsonar.projectKey=<projectKey>'
}

how should I run this task to avoid the Warning?

10

Hi @eradan,

I’m not sure you can. But you’re safe in ignoring it.

 
HTH,
Ann

1 Like