Skip to content

Fix passing down variables to release_environments pipeline

What does this MR do and why?

Fix passing down variables to release_environments pipeline

  • The dotenv variables are not used as pipeline variables in the downstream pipeline by default (doc). Thus, we have to specifically assign them to the trigger job's variables.
  • This change also removes the pass down of GIT_STRATEGY and GIT_DEPTH to the child pipeline. The child pipeline is in another repo - release-environments, thus using the same Git config as the parent pipeline doesn't make any sense.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

You can see the current issue by checking the variables of a downstream pipeline, like:

curl --header "PRIVATE-TOKEN: $GITLAB_COM_API_TOKEN" "https://gitlab.com/api/v4/projects/41365521/pipelines/1274124406/variables"

And you see that GIT_STRATEGY and GIT_DEPTH are passed down, but not the required variables ENVIRONMENT and VERSIONS.

Edited by Dat Tang

Merge request reports