Hey @qaz
With @7 of the SonarQube tasks, there are two JREs at play.
- One handling the download of the JRE on SonarQube (to support JRE auto-provisioning, basically to make things easier on users when someday we decide the minimum version of Java to run analysis should be Java 21)
- The JRE that is being downloaded from SonarQube, that actually runs the analysis (and handles further communication with SonarQube).
It seems like certs are working for the first JRE, but not the second.
You can disable JRE auto-provisioning (sonar.scanner.skipJreProvisioning=true) so that the first JRE handles everything.
Or you can make sure the right certs get passed to the second JRE (see the analysis parameters here).
We are aware this isn’t great and hopefully will make this smoother soon.