Open IkenoXamos opened 2 years ago
Hello, man! I solved this problem. You need to set this
sonarProperties:
sonar.ce.javaAdditionalOpts: "-javaagent:./lib/common/sonarqube-community-branch-plugin-${plugin_version}.jar=ce"
sonar.web.javaAdditionalOpts: "-javaagent:./lib/common/sonarqube-community-branch-plugin-${plugin_version}.jar=web"
Problem in folder, while sonarqube is starting up, folder extensions/plugins
does not contain any file. Only after startup and initialization (and this happens after setting the javaagent parameter)
but lib/common
already contains this plugin on current stage of initialization (if it's copied correctly, of course). And, if you refer to the right path that exists, everything will start and work :)
Enjoy!
Leveraging the Community Branch Plugin requires both installing a plugin as well as attaching the provided jar as a javaagent to both the web server process as well as the compute engine process.
I have used the below properties.
override.yaml:
where
${plugin_version}
is being substituted for1.8.1
.While standing up, I see that the plugin is downloaded by the
install-plugins
init-container:$ kubectl logs -c install-plugins sonarqube-sonarqube-649bd6ff78-75z99 -n sonar
However, the resulting pod fails with:
$ kubectl logs sonarqube-sonarqube-649bd6ff78-75z99 -n sonar
Notably, the 3 lines
Seems to indicate that the plugin jar file is not available for instrumenting. My best guess is that the additional Java opts are applied before the plugin has been received, so therefore fails to find it.
If I remove the
sonarProperties
configuration, the helm chart deploys successfully, and the plugin is shown as installed, however it does not function as intended, since sonarqube was not instrumented.