Trigger include is relative to root repo not the repo it is included from

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

• Close this issue

Summary

Child pipeline trigger include is relative to the root project not the project it is defined in.

Steps to reproduce

Project repo .gitlab-ci-yaml

include:
  - project: example
    file: child-pipeline.yml

Example repo child-pipeline.yml

stages: 
 - deploy

Deploy:
  stage: deploy
  trigger:
    include: deploy.yaml
    strategy: depend

Example repo deploy.yml

stages: 
 -test

Test:
  stage: test
  script: 
    - echo "Test"

Example Project

https://gitlab.com/max.bush/child-pipeline-include-issue/pipelines/150367189

What is the current bug behavior?

It loads deploy.yml from the root project not the project the included pipeline is defined in. If the deploy.yml file does not exist in the root project, the pipeline fails with a Local file deploy.yml does not exist! error message.

What is the expected correct behavior?

deploy.yml is loaded from the included yml pipeline e.g. (Example repo deploy.yml)