[Feature][Gitlab] Parsing CI/CD trigger jobs

[Marco-De-Stefani]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Use case

I would like to have the possibility to fetch the trigger jobs from GitLab CI/CD pipelines
https://docs.gitlab.com/ee/api/jobs.html#list-pipeline-trigger-jobs

Description

In my company, we have a setup where basically a main pipeline is triggering a child pipeline, which is responsible for the actual deployment (and from it I can have the actual environment where I'm deploying)
I know that GitLab doesn't offer an API to fetch those like we're fetching the pipelines, but the jobs need to be fetched for every single pipeline with the endpoint
projects/{{ ProjectId }}/pipelines/{{ PipelineId }}/bridges

I think it would be cool if we could have a setting for enable/disable this on the UI

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

[Startrekzky]

@d4x1 @abeizn Since it has to be collected by each pipeline, I think one logical solution to this is:

1. Add a collector for this GitLab bridge entity but make it optional
2. Support [Feature][Config UI] Allow users to decide which entities to collect for each data scope #5920 . Allow users to enable it in the Config UI

So I think it relies on the implementation of #5920