Sonarqube migration and upgrade

  • which versions are you using
    SonarQube developers edition Version 9.2.4 (build 50792)

  • how is SonarQube deployed
    zip

  • what are you trying to achieve
    We are in the middle of migration between openstack clusters. We’ve got Sonarqube deployed along with Postges.
    We would like to migrate sonarqube to the new cluster. Despite recommendation coming from the documentation it’s not possible to download exactly the same version of Sonarqube - not available in historic download page. At the end of migration we also would like to upgrade to the latest available LTS.

  • concerns

  1. can i migrate between developer and community edition not losing anything?
  2. what if i migrate from developer 9.2.4 to 9.9.6 community, start upgrading to the latest available and then elevate the edition back to the developers one - will that work?
  3. if i have to migrate to developer edition, can it be followed by consecutive upgrades to get the latest available version and keep Server ID, so i don’t have to request a new one after each bump?
  4. how i can avoid requesting for license update after each upgrade
  5. is there a list of sonarqube+postgres catalogs which could be moved to the vm deployed on the new openstack so I can have it operable without any special effort?
  • what have you tried so far to achieve this
    -migrating whole vm between openstacks clusters isn’t possible
    -creating a snapshot which could be migrated isn’t possible
    -moving volumes between the clusters isn’t possible
    -rsync failed
    -full postgress backup failed

Hi,

Welcome to the community!

Just do the upgrade as part of the migration.

You won’t lose any projects, Quality Profiles or Quality Gates. I suspect you won’t be able to see previously-analyzed branches and PRs in the UI anymore.

You could, but there’s no reason to make it that complicated. If this is a question of licensing, you should contact your sales rep.

Yes, of course.

You shouldn’t have to do this at all. The only time you would need a new license is if your JDBC URL changes. Make sure that stays the same and you should be good.

I’m not sure I understand the question, but I believe the answer is ‘no’.

 
HTH,
Ann