I want to run SonarQube in the cloud, most likely as an Azure Container App. What is the feasibility of having that scale to 0 most of the day?
I do not know how the SonarQube executables will react to that though, will they just time out etc.
I want to run SonarQube in the cloud, most likely as an Azure Container App. What is the feasibility of having that scale to 0 most of the day?
I do not know how the SonarQube executables will react to that though, will they just time out etc.
Hey there.
This is one of those things we’ve never tried and a great moment for you to try it out and let us know! I’m not sure how Azure Container Apps behave (is it just… waiting for an HTTP request and bringing up the app once it gets one)?
SonarQube is generally designed to always be up.
Indeed, Azure proxies your requests and will spin up a container when required. It will stay running for X minutes before spinning back down.
SonarQube is just a webUI in my experience so for 95% of the day it does not actually need to be running is how I figure.
My only concern will be how the sonarscanner handles this “lag” in initial response.
From a cold start, SonarQube will take at least 30 seconds or so to start. While that might not exceed timeouts from the scanner (which are also modifiable), that’s probably not a great experience for users who want to review analysis results.