Too excessive child pipeline variables inheritance
Project A config:
variables:
FOO: bar
trigger job:
trigger:
project: B
Project B config:
variables:
FOO: baz
job:
script:
- echo $FOO
Expected result:
baz
printed.
Actual result:
bar
printed.
This behavior is undocumented and overrides all variables in the downstream project with ones from the upstream. It would be nice to be able to control which variables should be passed to the downstream.