You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2020. It is now read-only.
It looks like the plugin system changed in recent Sonarqube versions, and hence, this puppet module doesn't work anymore.
If I use the puppet module to install the ldap plugin, it creates the file: /var/local/sonar/extensions/plugins/sonar-ldap-plugin-2.1.0.507.jar
The plugin is not recognized as installed.
When I install the ldap plugin from the web UI, the following files are created:
@telegrapher, can you document your setup? The filesystem shouldn't have changed, and we're successfully maintaining puppet with 5.6.6.
Can you check that the ldap plugin is actually getting placed in /usr/local/sonar/plugins/extensions (assuming your install root is usr/local) when you run your profile?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like the plugin system changed in recent Sonarqube versions, and hence, this puppet module doesn't work anymore.
If I use the puppet module to install the ldap plugin, it creates the file:
/var/local/sonar/extensions/plugins/sonar-ldap-plugin-2.1.0.507.jar
The plugin is not recognized as installed.
When I install the ldap plugin from the web UI, the following files are created:
And in sonar the plugin is recognized as installed.
The text was updated successfully, but these errors were encountered: