Recently, SonarQube uses the bintray repository for package distribution, in https (see update-center.properties).
Using the update center behind a
Is there today a mean to use the update center for these plugins ?
In sonar.properties
use sonar.web.javaAdditionalOpts
parameter to declare https.proxyXXX
properties :
sonar.web.javaAdditionalOpts=-Dhttps.proxyHost=proxy.company.com -Dhttps.proxyPort=80 -Dhttps.proxyUser=myUser -Dhttps.proxyPassword=myPassword
NB :
https.proxyUser
/https.proxyPassword
are useless if the same as http.proxyUser
/http.proxyPassword
further in the configuration.Perhaps one day some specific properties will be available in SonarQube config :-).
I tried updating sonar.web.javaAdditionalOpts in sonar.properties, but the settings were not picked up (using sonarqube:5.1.1 docker image).
I had to adapt the startup script:
My docker command:
RUN sed -i -e 's/-Djava.security.egd=/-Dhttps.proxyHost=proxy.mycompany.com -Dhttps.proxyPort=8080 -Dhttp.proxyHost=proxy.mycompany.com -Dhttp.proxyPort=8080 -Djava.security.egd=/g' /opt/sonarqube/bin/run.sh
The properties https.proxyHost
and https.proxyPort
are finally supported in SonarQube 5.5. Thanks Alix for the feedback.
https://jira.sonarsource.com/browse/SONAR-7429