Do I have to provide the license everytime I redeploy the sonarqube instance?

Must-share information (formatted with Markdown):

  • Sonarqube community 7.9.6 (will move to enterprise version)
  • automate the provisioning the license during instance startup
  • Tried nothing so far as I’m still in the investigation phase

So our sonarqube instance gets deployed via a pipeline and it gets redeployed a few times each year (BCM tests, some changes to plugins, etc). We are transitioning to the enterprise version and we were thinking how to provide the license during setup. The documentation shows I can provide the license in the UI or via an endpoint, but that requires the sonarqube instance to be up and running. I can make a script that does that, no problem. My question is do we need to provide the license everytime we redeploy the instance? Or does it gets saved in the database already that you only really need to do it once (even if you upgrade to a higher version, you won’t need to provide the license key again).

The license is stored in the database – so as long as the database isn’t redeployed (and started from scratch), you’re fine. Also, check out the documentation on License Management.

Also, your version is past EOL. You should upgrade to either the latest version or the current LTS at your earliest convenience. Your upgrade path is:

7.9.6 → 8.9.8 → 9.4 (last step optional)

You may find the Upgrade Guide and the LTS-to-LTS Upgrade Notes helpful.

Hi. Thank you for answer. Yes, we are in the process of upgrading our instance to the latest. However, we have decided that it’s worth moving from 7.9.6-community to 7.9.6-enterprise first, as it’s less risky.

To follow-up with the question, because the license is in the database, then theoretically it’s fine to do it once, correct? even with all the upgrades in the future, I don’t need to provide it.

Unless you meet the criteria in the docs mentioned that would cause your server ID to regenerate (and a new license needed) – correct, no need to provide it