Show API triggered pipelines in the pipeline graph
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Multi-project pipelines can now be triggered using a pipeline trigger token, creating a dependent pipeline relation that is visible on the pipeline graph.
Problem to solve
Pipeline trigger token allow triggering a pipeline via the API. When used from GitLab CI, the resulting trigger job will not behave like a bridge job and won't provide any information about the pipeline being triggered. Similarly, the triggered pipeline does not provide information about the triggering pipeline. This limits the usability of pipeline trigger tokens.
Pipeline trigger tokens are useful because they run in the context of the user creating the token. This allows separation of duties workflows, where the token is provided to another project which can then run pipelines in the triggered project without any project membership needs. This difference in membership is the major difference between triggering a pipeline via trigger token vs multi-project pipelines or triggering it via CI_JOB_TOKEN (https://docs.gitlab.com/ee/ci/jobs/ci_job_token.html#trigger-a-multi-project-pipeline-by-using-a-ci-job-token)
Proposal
Align triggering a pipeline via pipeline trigger token with triggering a pipeline via CI_JOB_TOKEN, allowing it to create a dependent pipeline displayed in the pipeline graph
Intended users
Feature Usage Metrics
Number of pipelines triggered via pipeline trigger token Number of users triggering a pipeline via pipeline trigger token