[SQ] API GET '/api/server/version' failed, error is The operation was aborted

SonarQube Server / Community Build
1

Hi, I am trying to integrate SonarQube with our Azure DevOps pipeline. The pipeline code is as below

trigger:
- develop
- feature/*

pool:
  vmImage: ubuntu-latest

steps:
 - checkout: self
 - task: SonarQubePrepare@6
   inputs:
     SonarQube: 'SonarQube'
     scannerMode: 'CLI'
     configMode: 'manual'
     cliProjectKey: 'WebCore_WebCore_4d22736d-9a9c-49f3-9182-9e41d8c96faf'
     cliProjectName: 'WebCore'
     cliSources: '.'
     extraProperties: |
        sonar.verbose=true

 - task: SonarQubeAnalyze@6
   inputs:
    jdkversion: 'JAVA_HOME_17_X64'

 - task: SonarQubePublish@6
   inputs:
     pollingTimeoutSec: '300'

but I am error as below (the whole log)

Starting: SonarQubePrepare
==============================================================================
Task         : Prepare Analysis Configuration
Description  : Prepare SonarQube analysis configuration
Version      : 6.3.2
Author       : sonarsource
Help         : [More Information](https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops/)
==============================================================================
##[warning]Error while executing SonarQube:Prepare task: [SQ] API GET '/api/server/version' failed, error is The operation was aborted.
##[error][SQ] API GET '/api/server/version' failed, error is The operation was aborted.
Finishing: SonarQubePrepare

I see in the service connection it was accessed

image
image1268×675 22.4 KB

What can be wrong? I did everything as on the SonarQube tutorial, available on our internal & not exposed server.

2

Hi,

I’m not sure I’ve seen this particular error before. The api/server/version call is the very first contact the scanner makes with the server, so there’s a basic communication problem between the two.

As a first step, you should double-check the SonarQube URL you’ve configured in your global settings under the ‘SonarQube’ configuration name. If that URL is correct, then I would look at what sits between scanner and server that might be aborting the connection (because this is not something the scanner does).

 
HTH,
Ann

3

Thank you for the quick reply!

As a first step, you should double-check the SonarQube URL you’ve configured in your global settings under the ‘SonarQube’ configuration name
I just copy-pasted (even clicking on the button) the URL provided in the tutorial, so…

A control question - does our server need to be exposed to the internet?
Do I need to somehow configure the sonarQube connection, like checks or something?

4

Hi,

Counter question: where do your build agents live? Your SonarQube server needs to be accessible from the build agents, wherever that is.

Sorry, I don’t understand question.

 
Ann

5

for SonarQube the current agent is hosted by MS, default setup, Azure pools

image
image1429×271 13.7 KB

That is the only build agent currently used; we have another azure pipeline in preparation, but that is out of the scope - I think you are not asking about that, but about the environment which is hosting the mentioned job.
The SonarQube worker is on another - in local network - server.

Regarding connection, there is that tab on the screen below - it was not mentioned to change there anything, but maybe?

image
image1367×815 74.7 KB

6

Hi,

From a brief skim ‘Approvals and checks’ doesn’t look like something you’d need to set up on a first pass.

 
HTH,
Ann

7

Thank you for the clarification.
But, regarding the abort, should the worker machine be exposed to the internet, or it is not necessary? I ask because for the self hosted workers (for normal azure pipeline) it is not required - it works in the pooling way. But what about the sonar qube worker, if the agent is MS hosted?

8

Hi,

Your build agent needs to talk to your SonarQube server, so whatever that means network-wise. You probably want to talk to your network folks.

 
HTH,
Ann

9

Thank you!

10

3 posts were merged into an existing topic: Prepare Analysis Configuration Fails in version 6.3.2

11

On my side the problem was the address was not accessible from the internet… a bit quirky but ok.

At the end I put the agent on the same machine as sonar qube worker.

1 Like