Pipeline fails when project includes another project yaml and compliance yaml
Summary
When the project is configured with custom CI file (gitlab-ci.yml@namespace/group-1/project-1), project pipelines fails with an error “Pipeline cannot be run. Included file .gitlab-ci.yml@namespace/group-1/project-1
does not have YAML extension!”
##Steps to reproduce
- Create a project
group-1/project-1
that has compliance pipeline yaml. For example -base-compliance.gitlab-ci.yaml
- Create a compliance framework
XYZ
pointing to the above compliance yaml i.e.base-compliance.gitlab-ci.yaml@group-1/project-1
- Create another project
group-1/project-2
that has the CI pipeline yaml file i.e.common-fragment.gitlab-ci.yaml
- Create another project
group-1/project-3
and updateCI/CD configuration file
in pipeline settings to use CI file ingroup-1/project-2
i.e.common-fragment.gitlab-ci.yaml@group-1/project-2
- Apply compliance framework
XYZ
togroup-1/project-3
and run the pipeline forgroup-1/project-3
Example project with failing pipeline
What is the current bug behaviour?
The pipeline fails with the following error: Included file
common-fragment-gitlab-ci.yml@group-1/project-2 does not have YAML extension!
What is the expected correct behaviour?
The pipeline should run both the compliance framework yaml and the project yaml