Using SonarQube Marketplace
You can only install and update plugins from the Marketplace in SonarQube Community Build. With commercial editions, you need to manually install and update your plugins. See Install a plugin for more information.
Your SonarQube Community Build instance needs internet access to check for and install plugin updates. Installations require restarting the platform before they take effect.
A third-party website called sonarplugins.com also exists. This website is not the same as the Marketplace and is not endorsed by, affiliated with, maintained, authorized, or sponsored by Sonar.
Pending operations
When you perform an action in the Marketplace (install, update, or uninstall a plugin), a yellow banner appears at the top of the page showing pending operations that will be executed once SonarQube Community Build is restarted. Pending operations can be canceled until the server is restarted.
Restart SonarQube Community Build
Restarting SonarQube Community Build can be done manually from the command line by running sonar.sh restart. In SonarQube Community Build, you can also restart from the UI, in the Update Center. When you have Pending Changes, the restart button will be displayed in the yellow banner (see Pending Operations above). Please note that restarting SonarQube Community Build won't reload the changes applied to the sonar.properties.
Stopping the Marketplace from searching for plugin updates
Your SonarQube Community Build needs internet access for the Marketplace to search for plugin updates. If your server doesn't have internet access, you may get errors in your logs when the Marketplace tries to search for new plugins. You can stop this by updating sonar.updatecenter.activate in <sonarqubeHome>/conf/sonar.properties.
Which URLs does the Marketplace connect to?
The SonarQube Marketplace connects to https://downloads.sonarsource.com/?prefix=sonarqube/update to get the list of plugins. Most of the referenced plugins are downloaded from:
Using the Marketplace behind a proxy
Marketplace uses HTTP(S) connections to external servers to provide these services. If SonarQube Community Build is located behind a proxy, additional information must be provided in <sonarqubeHome>/conf/sonar.properties:
http.proxyHost=<your.proxy.host>
http.proxyPort=<yout.proxy.port>
#If proxy authentication is required
http.proxyUser=<your.proxy.user>
http.proxyPassword=<your.proxy.password> Note: the same properties can be used in the https.* form for HTTPS connections.
Deploying to the Marketplace
If you have developed a SonarQube plugin, you can check out the requirements for adding it to the Marketplace in the Plugin Development community.
Was this page helpful?
© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARQUBE, and CLEAN AS YOU CODE are trademarks of SonarSource SA.
