Hello,
I’m attempting to integrate a instance of SonarQube community edition with a Gitlab self-managed instance. I followed the docs for Gitlab integration and was successful in creating the configuration (linking sonar to my Gitlab using its URL and an Access Token.
Subsequently, I was successful in importing a test Gitlab project/repo I created to test integration.
For context, both the Sonarqube and Gitlab instance are hosted on AWS EC2. The networking/security rules are in place to allow communication. I’m trying to integrate the Sonar scans into jobs running on self-managed Gitlab runners (also on a separate EC2) and using docker executor.
Currently, the runner picks up the job and uses the provided image but fails with “unable to reach server”…that being the address of the Server Base URL I set on Sonarqube. This is also the Gitlab environment variable set for SONAR_HOST_URL. Granted, this is a test server and the real URL is http://ip-.../us-gov-west-1/compute/9000 for Sonarqube etc.
I think my main question is- do I need a registered domain name with a public cert, DNS registration, along with a load balancer and reverse proxy like nginx to allow Sonarqube to be reachable by my CI runner?