Sonarcube integration with azure pipeline

Question about sonarcube integration with azure pipeline?, we have a separate sonarcube server vm but this vm doesn’t have public ip address, it only runs on internal ip address with vpn. When Sonar Cube is integrated into Azure Pipeline, Azure Pipeline cannot be integrated into that VM.

We get the error message:
##[error][SQ] API GET ‘/api/server/version’ failed, error was: {“errno”:“ETIMEDOUT”,“code”:“ETIMEDOUT”,“syscall”:“connect”,“address”:“”,“port”:9000}

Please let me know if there is any other way to integrate with the azure pipeline on VM server with internal IP address.

Hey there.

Your SonarQube server will need to be accessible by the pipeline – whether that’s an Azure DevOps-hosted agent or a self-hosted agent. There’s really no way around this.

Thanks for you updates.

I have one more questions:
Do we need a public IP address to run SonarQube in Azure Pipeline? Can’t we access sonarQube in azure pipeline without public IP?


Your internal resources are going to have to be accessible from your external resources. Are there any other cloud services that are interacting with your internal resources – how are they doing it (a proxy, a gateway, something else…)

1 Like