You can simply put a sonar.properties file under /opt/docker-sonar/conf/. This file will be available inside the container under /opt/sonarqube/conf/, because the folder gets mounted as volume.
A full example for a sonar.properties file can be found on github. However all you need to enter is:
sonar.ce.javaOpts=-Xmx<XMX_VALUE -Xms<XMS_VALUE> -XX:+...
Any CI/CD plugin can ultimately be scripted. However, using plugins gives you better centralized control.
Consider the following scenario: Your SonarQube server location has to move to a new location.
If you are using a script like the example you provided above, you would need to manually update every script. This process is error prone as you may ...
Ok no so obvious but at least one possible way is:
Note the component ID in the TravisCI report
Use the ID and this documentation to get data:
Please refer to the following article on the SonarQube - SonarScanner setup best practices. It will be good if the following hardware recommendations are considered for the SonarQube installations. Following are some of the important considerations.
SonarQube server should be on a real DB not on H2.
The analysis should occur very close to the SonarQube DB.
I have added "C:\Program Files\Java\jdk-12.0.2" as value of JAVA_HOME environment Variable and its working. I don't know exactly this is the correct solution OR Not, but when I have checked sonar-scanner.bat file then it's taking %JAVA_HOME%/bin/java.exe location of Java.
Create and add token to be able to connect to SonarQube.
You have create project in SonarQube and use it as a parameter:
Copied from [StackOverflow] Problem with Connecting Jenkins to SonarQube.
If you mean removing a "snapshot" of an analysis according to the most recent SonarQube documentation you should be able to this. Also if you have access to the database SonarQube is using then you could remove the analysis directly from there. That option may introduce other issues though depending on how SonarQube handles it.