Ensure all ENV variables are propagated to codequality job

Problem to solve

Our ~"code quality" job supports several ENV variables to configure the log levels, timeouts, and source code path. These are supported using the previous job definitions but it doesn't look like our variables are properly propagated to the containers when using our included CI templates. We should update the templates to properly pass the supported ENV variables.

Intended users

Persona: Software developer

Proposal

Update CI templates to pass all supported ~"code quality" ENV variables.

Testing

TIMEOUT_SECONDS can be passed explicitly within gitlab-ci.yml variables in order to ensure job timeout more quickly than 900 seconds; i.e.

variables:
 TIMEOUT_SECONDS: 1

include:
  - Code-Quality.gitlab-ci.yml

What does success look like, and how can we measure that?

Users can use templates with configurable environment variables.

What is the type of buyer?

GitLab Core

Links / references