Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project name is "" in cases where trigger is based on included artifact and artifact is a ci.yaml file. #98

Open
mercury200Hg opened this issue Jan 26, 2024 · 1 comment

Comments

@mercury200Hg
Copy link

If a project uses ci.yml produced as an artifact then the relationship of the trigger should be the source project of the artifact but instead it's currently marked as ""

Steps to reproduce:

If your .gitlab-ci.yml contains following syntax:

trigger:
    include:
      - artifact: child-ci.yml
        job: my-job

In that scenario the name of project in relationship is marked "" whereas it should either be should be the source project of the artifact.

@mercury200Hg mercury200Hg changed the title Project name is "" in cases where trigger based on included artifact and artifact is a ci.yaml file. Project name is "" in cases where trigger is based on included artifact and artifact is a ci.yaml file. Jan 26, 2024
@catouc
Copy link
Owner

catouc commented Jan 26, 2024

Yeah the parsing is missing logic for dynamic child pipelines, as per https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html#dynamic-child-pipelines. Will try to have a look the next few days, it will require to throw out the parsing logic again in large parts so might take a bit longer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants