Brownout Notice: Phasing out Java < 21 as a Scanner Runtime on SonarQube Cloud

Sonar Updates
, , ,
1

Hi,

As previously communicated in Phasing out Java 17 as a Scanner Runtime we are going to stop supporting Java runtime lower than 21 to run Sonar analysis.

Despite the warning in logs and in the SonarQube UI, we are still observing in our telemetry that a few analyses are still run using a Java runtime < 21.

That’s why we are going to run a scheduled brownout, starting today (July, 7th). Analyses running on SonarQube Cloud with a Java runtime < 21 will fail between 1:00 PM GMT and 2:00 PM GMT every day.

We are aiming to fully stop supporting Java runtime < 21 starting from July, 13th July 20th.

4

Hi Julien,

Would you be able to post this sort of brownout ahead of time on your Statuspage, as scheduled maintenance events? That will trigger email notifications that are useful for planning ahead.

If you had the minimum supported versions (SonarScanner >= 6 with JRE auto-provisioning) in the notice then people could do a quick grep to see if they’ll be impacted.

I looked back and in 2020 you were able to send targeted emails with a list of projects to upgrade way back when Java 8 support was removed. That’s a little more than I’d expect, but it was handy at the time for identifying a couple of lower-traffic projects we’d missed.

Thanks,

Mike

5

Hi @ms1111

Good point, I will try to make it for the next time.

I think all the details were in the original announcement I linked: Phasing out Java 17 as a Scanner Runtime

Thanks, I will try to see how this was implemented, and see if we could do it again.