Trigger pipeline job is pending when using a variable as value of one of its parameter

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

When using a variable as a value of one of the parameter of the trigger action in a gitlab-ci.yaml file, the job stays in pending state and does not trigger the sub-pipeline. It is useful to trigger another project pipeline in the same branch as the current pipeline branch. By replacing the variable $CI_COMMIT_REF_NAME as the value of the branch trigger parameter by a constant value, the trigger works as expected.

Steps to reproduce

• Add a trigger job
• use a variable as the value of the branch parameter

Example Project

https://gitlab.com/drousselie/test project should trigger https://gitlab.com/drousselie/test2 project on the same branch as the running pipeline (master or test_pipeline branches).

What is the current bug behavior?

The trigger job stays in pending state.

What is the expected correct behavior?

The trigger job should trigger the other project on the same branch as the current pipeline.

Output of checks

This bug happens on GitLab.com