Azuredevops SonarQubePublish@4- Error: tunneling socket could not be established, statusCode=502

SonarQube
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  • how is SonarQube deployed: zip, Docker, Helm - Docker
  • what are you trying to achieve - to integrate SonarQubePublish task to implement in pipeline successfully
  • what have you tried so far to achieve this - googled it for solution but no luck

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

#################

Hi Sonar Support team,

We installed SonarQube as docker
this task is peen performed on azure devops
we need your help on to understand and get some sort of help for below mentioned AzureDevops pipeline SonarQubePublish task

Note :-
SonarScan ANALYSIS is SUCCESSFUL, we can browse it at SonarQube application project end.
Post this we are executing SonarQubePublish@4 task and it failed with → Failed to create a build property. Not blocking unless you are using the Sonar Pre-Deployment gate in Release Pipelines. Exception : Error: tunneling socket could not be established, statusCode=502

Below is the azure pipeline snippet that is been called
- task: sonarsource.sonarqube.291ed61f-1ee4-45d3-b1b0-bf822d9095ef.SonarQubePublish@4
continueOnError: true
displayName: “Publish Quality Gate Result”

Error output of the task

Starting: Publish Quality Gate Result

Task : Publish Quality Gate Result
Description : Publish SonarQube’s Quality Gate result on the Azure DevOps build result, to be used after the actual analysis.
Version : 4.9.1
Author : sonarsource
Help : Version: 4.9.1. More Information

SYSTEMVSSCONNECTION exists true
SYSTEMVSSCONNECTION exists true
##[warning]Failed to create a build property. Not blocking unless you are using the Sonar Pre-Deployment gate in Release Pipelines. Exception : Error: tunneling socket could not be established, statusCode=502
Finishing: Publish Quality Gate Result

2

There exists release @5 of all the SonarQube tasks, e.g. SonarQubePrepare@5. We just changed the digit, maybe you want to give it a try. I don’t know if it might help for your problem.