@@ -92,6 +92,7 @@ define a `CUSTOM_CA_CERTS` variable either as a group/project variable, or in it
But there is also a global way to fix this. Ask your GitLab administrator to declare `DEFAULT_CA_CERTS`
as an [instance-level CI/CD variable](https://docs.gitlab.com/ci/variables/#for-an-instance).
Similar to `CUSTOM_CA_CERTS`, `DEFAULT_CA_CERTS` shall contain one or several certificates in [PEM format](https://en.wikipedia.org/wiki/Privacy-Enhanced_Mail).
Similar to `CUSTOM_CA_CERTS`, `DEFAULT_CA_CERTS` shall contain one or several certificates in [PEM format](https://en.wikipedia.org/wiki/Privacy-Enhanced_Mail), and can either be a
[file-typed](https://docs.gitlab.com/ci/variables/#use-file-type-cicd-variables) variable or basic environment variable.
Every _to be continuous_ template job - prior to executing - determines whether a `$CUSTOM_CA_CERTS` or else `$DEFAULT_CA_CERTS` is defined and adds its content to the trusted CA certificates.
@@ -325,6 +325,8 @@ Again, you may perfectly set `CUSTOM_CA_CERTS` in your project:
* either locally in specific jobs,
* or for all jobs from one single template ([see below](#the-templates-base-job)).
ℹ️ `CUSTOM_CA_CERTS` can either be a [file-typed](https://docs.gitlab.com/ci/variables/#use-file-type-cicd-variables) variable or basic environment variable.
