sonarqube - Upgrade and move Sonar Server 2.13.1 -> 4.5.6LTS - Before starting -


on production server rhel 6.3 (box1) run jenkins ver. 1.565.1 (sonar plugin 2.1); maven ver. 3.0.5; java ver. 1.7.0_51; mysql ver. 5.1.61 (innodb engine); sonarqube ver. 2.13.1 (no sonar plugin used).

i upgrade sonar 2.13.1 sonar 4.5.6 it's last lts upgrade process following: 2.13.1 -> 3.7.4 -> 4.5.6 (two steps)?

plus, sonar moved/upgraded on different box (box2) , mysqldb on third 1 (box3).

related questions:

  • will data preserved doing dump/restore?
  • can have box3 on dedicated production db network: 192.x.x.x (while box1 , box2 in same - 172.x.x.x) or mandatory have them on same network? alternatively better have box2 = box3 or none of 2 configurations?

extra question: upgraded version of official documentation shows analizers doesn't talk sonar db while previous version states do. means sonar version behavior changes , not impact upgrade process?

thank you, leonardo

you can upgrade directly 2.13.1 4.5.6. it's after 4.5.6 must hit every lts between current version , target version.

moving db different box: follow db vendor's recommendation moving db different machine, connect sq server db @ new location & make sure looks right. should it. can upgrade before or after move, make sure - stated in normal upgrade procedure - db first.

proximity on network of analysis , db boxes: tie database during analysis cut in 5.2. since you're upgrading 4.5.6, you'll want keep these 2 boxes close each other, network-wise. note i'm referring machine on analysis runs, distinct 1 running server.


Comments

Popular posts from this blog

php - Wordpress website dashboard page or post editor content is not showing but front end data is showing properly -

How to get the ip address of VM and use it to configure SSH connection dynamically in Ansible -

javascript - Get parameter of GET request -