Improvement implemented and will be available in the next release.

I have tried the suggested solution with a withSonarQubeEnv block, i.e.

withSonarQubeEnv(<SonarQube installation ID>) {
  step([$class : 'InfluxDbPublisher',
  customData : null,
  customDataMap : null,
  customPrefix : null,
  customProjectName: null,
  target : 'jenkins_data'])
}

Unfortunately I still get HTTP 401. I have verified that SONAR_AUTH_TOKEN is set inside the block, but it's not accessible to the InfluxDB plugin, it is still null. Perhaps I am doing something wrong. Have you been able to verify the fix with Jenkins pipeline, aleksisimell?

Running plugin version 1.14.

Confirmed that this doesn't work in a Jenkins declarative pipeline

Can someone post an example snippet on how to pass the Auth Token to the plugin in a jenkins Pipeline. It works fine if i add a JUnit in the code base but i am not able to pass it from Pipeline to the plugin in a real environment.

Problem still occurs with Plugin Version 1.20.

Jenkins: 2.150

SonarQube: 7.1

The Token is valid and Environment Variable "SONAR_AUTH_TOKEN" is set with the correct value

I managed it to send the Authentication using a "Jenkins Global Environment Variable" named "SONAR_AUTH_TOKEN".

Also it is important (using SonarQube  7.4 and InfluxDB Plugin 1.20.1) to set an Environment Variable "SONAR_HOST_URL".

forster_ch Are you using Jenkins Pipeline?

jl68: yes

This seems to be an issue with some kind of scope (I am not terribly familiar with the inner workings of jenkins).

Using the WithSonarQubeEnv provides the auth token and host url, but the InfluxDB plugin seems not to be able to access it (even tho it reads this variable in the same exact way as the host url, which succeeds). BUT as a workaround, doing as forster_ch mentioned, setting the sonar auth token as a GLOBAL env variable (that is, Manage Jenkins -> Configure System -> Global properties -> Environment variables, enable and add SONAR_AUTH_TOKEN). This is insecure, since this kind of information is supposed to be handled by Credentials Provider, so use only in dire situations. I am confident that aleksisimell will find the root cause to this and correct it (I made a small PR relating to this, wink wink).

And to add, I am using the Multibranch Declarative Pipelines when testing this.

Issue fixed with https://github.com/jenkinsci/influxdb-plugin/pull/74. Will be available in next release.