[JIRA] (JENKINS-47776) sonarqube integration doesn't authenticate

I have tried the suggested solution with a {{withSonarQubeEnv}} block, i.e.
{code:java}
withSonarQubeEnv(<SonarQube installation ID>) {
step([$class : 'InfluxDbPublisher',
customData : null,
customDataMap : null,
customPrefix : null,
customProjectName: null,
target : 'jenkins_data'])
}{code}
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.

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

jonas.d.lindstrom@netent.com (JIRA)

unread,

Apr 13, 2018, 10:11:02 AM4/13/18

to jenkinsc...@googlegroups.com

Jonas Lindström commented on

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, Aleksi Simell?

cwebb@thoughtworks.com (JIRA)

unread,

Apr 17, 2018, 5:50:03 AM4/17/18

to jenkinsc...@googlegroups.com

Christopher Webb reopened an issue

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

Jenkins /

sonarqube integration doesn't authenticate

Change By:	Christopher Webb
Resolution:	Done
Status:	Resolved Reopened

trysharmaji@gmail.com (JIRA)

unread,

Jun 26, 2018, 9:37:02 PM6/26/18

to jenkinsc...@googlegroups.com

Rahul Sharma commented on

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.

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

christoph.forster@swarovski.com (JIRA)

unread,

Nov 7, 2018, 3:08:02 AM11/7/18

to jenkinsc...@googlegroups.com

Christoph Forster commented on

Problem still occurs with Plugin Version 1.20

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

christoph.forster@swarovski.com (JIRA)

unread,

Nov 7, 2018, 3:31:02 AM11/7/18

to jenkinsc...@googlegroups.com

Christoph Forster edited a comment on

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

christoph.forster@swarovski.com (JIRA)

unread,

Dec 3, 2018, 9:05:02 AM12/3/18

to jenkinsc...@googlegroups.com

Christoph Forster commented on

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".

Nevertheless I receive a JSonException now, but this is another Problem ...

christoph.forster@swarovski.com (JIRA)

unread,

Dec 3, 2018, 9:07:02 AM12/3/18

to jenkinsc...@googlegroups.com

Christoph Forster edited a comment on

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".

Nevertheless I receive a JSonException now, but I don't receive JSon Content but the loading page of SonarQube this is another Problem ...

christoph.forster@swarovski.com (JIRA)

unread,

Dec 19, 2018, 7:48:02 AM12/19/18

to jenkinsc...@googlegroups.com

jonas.d.lindstrom@netent.com (JIRA)

unread,

Dec 19, 2018, 8:01:03 AM12/19/18

to jenkinsc...@googlegroups.com

Jonas Lindström commented on

Christoph Forster Are you using Jenkins Pipeline?

christoph.forster@swarovski.com (JIRA)

unread,

Dec 19, 2018, 9:33:02 AM12/19/18

to jenkinsc...@googlegroups.com

Christoph Forster commented on

Jonas Lindström: yes

axel@latvala.com (JIRA)

unread,

Jul 1, 2019, 9:35:06 AM7/1/19

to jenkinsc...@googlegroups.com

Axel Latvala commented on

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 Christoph Forster 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 Aleksi Simell will find the root cause to this and correct it (I made a small PR relating to this, wink wink).

axel@latvala.com (JIRA)

unread,

Jul 1, 2019, 9:36:03 AM7/1/19

to jenkinsc...@googlegroups.com

Axel Latvala edited a comment on