vanderby / SonarQube-AzureAppService

Instructions and files to host SonarQube on an Azure App Service without a container.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

upgrade versions in-place?

Curbed-Enthusiasm opened this issue · comments

commented

Per the title, is it possible to upgrade versions in place? Is it recommended?

Currently we've been using this at 8.7, and don't see any issues upgrading. The solution has treated us well so far, we're just trying to keep things up-to-date where we can.

I'm glad you've found it useful!

You can do upgrades in the normal fashion by replacing the sonar folder in the wwwroot folder with the new bits using Kudu or ftp.

You could also create a deployment slot, backup the database, update the connection string and update the deployment slot with the new bits to test the upgrade. Then do a slot swap when you have verified everything works. Keep the connection string as a slot setting so you don't accidently switch your prod db to the backup with the slit swap.

-Nate

commented

sweet! thanks for the response! I'll give that a shot and report back in case anyone else finds it useful.

Hello Vnaderby, I thank you very much and I found it so useful, currently I have an App Service deployed with your template in a 8.6 community version and I am trying to update it to an enterprise version and the most current possible, but I do not understand much how to do it from the slot, I am doing what following and I do not know if you can help me:

  • From "Deployment Slots"> "Add Slot"> Name: XXX> Clone settings from: "Prod Slot"
  • I did the back up for the DB
  • I cloned de setting and I understand that the connection string is the same, ok?:
    "name": "sonar.jdbc.url",
    "value": "jdbc:sqlserver://....."
  • In the step "update the deployment slot with the new bits to test the upgrade"
    • Do I need to copy the "site" folder from the production slot with the new bits and run HttpPlatformHandlerStartup.ps1?

I thank you in advance, attentive to your comments

Hey @thermick, you can update the bits by downloading them from SQ's website then uploading them via FTP or App Service's Kudu backend or any other standard means of moving bits to an Azure App. Service.

commented

Just as a late follow-up because this upgrade was pushed back due to higher priority roadmap items. For testing I stood up a second instance using your repo, and backed up our prod db and hooked it up to the secondary instance then ran the upgrade steps via sonarqube's instructions and the FTPS settings in the app service. Unfortunately I just couldn't get the swap slot to work properly, but I just moved to an azure shop from an AWS one so I'm still learning some ins and outs. It was incredibly easy and worked like a charm, and the behavior was exactly the same when I ran everything on prod.

Thanks again for putting all this together!