Package Details: sonarqube

Git Clone URL: (read-only, click to copy)
Package Base: sonarqube
Description: An open source platform for continuous inspection of code quality
Upstream URL:
Licenses: LGPL3
Conflicts: sonarqube-lts
Provides: sonarqube
Submitter: gizyou
Maintainer: schard
Last Packager: schard
Votes: 21
Popularity: 0.012379
First Submitted: 2015-11-08 17:36
Last Updated: 2021-07-20 17:56

Dependencies (4)

Required by (0)

Sources (5)

Latest Comments

1 2 3 Next › Last »

satiricon commented on 2021-06-25 23:07

I had to add this to the service to make it work.



hashworks commented on 2020-11-05 10:14

/usr/lib/systemd/system/sonarqube.service:{11,12}: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

quebin31 commented on 2019-10-23 19:26

@dNhax please fix java-runtime dependency, as stated here, Sonarqube only supports java 11, not above that.

dNhax commented on 2018-10-09 07:48

@sigman: Thanks for pointing that out! I will update the package after work.

sigman commented on 2018-10-09 06:26

Since now requires credentials, I managed to install it after changing base url to:

MoroS commented on 2018-07-10 18:36

@attila123: Just to supplement dNhax's answer, you got the "Permission denied", because SonerQube operates on a system service level and assumes, that it has that very level of file system access. That being said, you can easily run it like you mentioned as root (although you should use "systemctl start sonarqube" to be on the safe side and let SystemD manage it as a service).

dNhax commented on 2018-07-10 17:25

@attila123: After package installation, start or enable sonarqube.service with systemd.

attila123 commented on 2018-07-10 15:08

What is the easiest way to get it running (locally, kind of just to try out)? According to I tried to run it as normal user (/usr/share/sonarqube/bin/linux-x86-64/ console), and got some permission problems (not sure what it was, maybe some log file). I tried it running as root, but then got jvm 1 | 2018.07.10 16:50:11 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 1 and /var/log/sonarqube/es.log contains the problem: java.lang.RuntimeException: can not run elasticsearch as root

I run it again as normal user to note down the permission problems:

$ /usr/share/sonarqube/bin/linux-x86-64/ console
Running SonarQube...
wrapper  | ERROR: Could not write pid file /usr/share/sonarqube/bin/linux-x86-64/./ Permission denied
Unable to open logfile ../../logs/sonar.log: Permission denied

I ended up brute force fixing the permission problems:

sudo chown -R $USER:mygroup /usr/share/sonarqube
sudo chown -R $USER:mygroup /var/log/sonarqube

Not it works, but I am not sure how is it supposed to work.

dNhax commented on 2018-07-03 16:17

Those warnings are harmless and can be ignored.

MoroS commented on 2018-07-02 17:39

@dNhax: upgraded. Works like a charm. :)

Just one question about this:

warning: could not get file information for usr/share/sonarqube/extensions/plugins/sonar-python-plugin-
warning: could not get file information for usr/share/sonarqube/temp/README.txt

It doesn't do anything harmful (in my case at least). I was just wondering if this is related to the "Non-default plugins have been deleted." message seen a bit later? As in part of the cleaning up process?