Skip to content

[SonarQube Template] Using default ca certs

Describe the bug

I use Sonarqube template with httpS sonarqube server. The cert is not read properly. Indeed, with DEFAULT_CA_CERTS and without CUSTOM_CA_CERTS, the result analyses is not sent to the server and the job fails. With the CUSTOM_CA_CERTS, the job is in success.

Expected behavior

With the HTTPS sonarqube server, the analysis is can be sent only using the global variable DEFAULT_CA_CERTS.

Actual behavior

The job failed if the CUSTOM_CA_CERTS is not set.

Logs and/or screenshots

With only DEFAULT_CA_CERTS image

With both certs (same value), it works image

Context & Configuration

Where I set the CUSTOM_CA_CERTS, I put the same value than in DEFAULT_CA_CERTS.

Only with the DEFAULT_CA_CERTS variable, the following templates works well:

  • gitlab-sync
  • dependancy-track

The issue was reproduced using:

  • Version of the template: 4.2.4
  • GitLab server(s): A self-managed server Free Gitlab v17.5.2-EE
  • GitLab runner(s): type docker v17.5.3

Configured GitLab CI project or group variables:

With only global variable, it does not work

  • DEFAULT_CA_CERTS

With the two variables, it works

  • DEFAULT_CA_CERTS (global)
  • CUSTOM_CA_CERTS (on the project)
Edited by Emmanuel Scrizzi