SonarQube
Before you install
Section titled “Before you install”These answers used to sit on this app’s store listing. They moved here on 2026-08-17: a shopper deciding whether to install is not reading six hundred words of Q&A, and the listing page is the pitch. The knowledge is no less true for being off the storefront: it is the part you want before you commit, which is what a guide is for.
Which edition is this?
Section titled “Which edition is this?”The SonarQube Community Build. Everything on this page is Community behaviour, limits included: one GitLab configuration, and no merge-request decoration. The package is built around those limits rather than around an upgrade you have not bought.
Do I need GitLab to use it?
Section titled “Do I need GitLab to use it?”No. The GitLab integration is optional: without it you get SonarQube with its own projects and its own tokens. With it, the binding and the scanner credentials are created for you when the deployment converges.
What licence is the Community Build under?
Section titled “What licence is the Community Build under?”The package records it as unverified, and that is deliberate. LGPL-3.0 is widely reported upstream, but nothing in this repository proves it, and a catalogue that asserts licences it has not checked is worse than one that admits the gap.
Moving its database
Section titled “Moving its database”What happens to the server ID when the database moves?
Section titled “What happens to the server ID when the database moves?”SonarQube stores a checksum of its JDBC URL next to its server ID (sonar.core.id in its properties table) and checks it at every start. A postgres repoint (shc update <stack> -i postgres=<provider>) or a restore onto another engine changes that URL, so the first start after it mints a new server ID. The rows move intact. Only the ID changes. Moving back onto the old engine mints a third ID rather than restoring the first.
The Community Build binds nothing to the ID, so nothing breaks. SonarSource issues a Developer or Enterprise licence against it: read the server ID under Administration > System before the move, and have the licence re-issued against the new one after it.