SonarQube scan action (GitHub) v4.0.0 failing - keytool command not found

SonarQube Server / Community Build
,
12

Hi @higgs01,
Thanks a lot for your super-quick update!

Yes, technically we should create a new ticket for this issue specifically, but let’s just continue here for convenience.

From your logs, it seems that the keytool is invoked correctly, and that
~/.sonar/ssl/truststore.p12 has been created. But somehow the p12 is not taken into account by the SonarScanner CLI, in the actual scan.

Could you please run the SonarScanner CLI in debug mode and report the logs here?

You can either add RUNNER_DEBUG: 1 to your environment variables, like so:

    - name: SonarQube Scan
      uses: sonarsource/sonarqube-scan-action@v4.1.0
      env:
        RUNNER_DEBUG: 1

or -Dsonar.verbose=true to the args parameter of the GitHub action, like so:

- uses: sonarsource/sonarqube-scan-action@v4.1.0
  with:
    args: >
      -Dsonar.verbose=true

Whatever comes easier to you.

This should gives us more information about the execution of the scan by the SonarScanner CLI. In particular, we are looking for a log line like the following:

DEBUG Using truststore: /home/runner/.sonar/ssl/truststore.p12

Thanks,
Antonio