Skip to content

CI_JOB_TOKEN cannot access Bridge job API which prevents finding child / cross-project pipelines

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

The CI_JOB_TOKEN has access to several API endpoints as documented here: https://docs.gitlab.com/ci/jobs/ci_job_token/#job-token-access

It can also be given access to read from other projects, as documented here: https://docs.gitlab.com/ci/jobs/ci_job_token/#control-job-token-access-to-your-project

However, the big missing gap is no access to the bridges API to simply read the 'bridge' job created for child pipelines in the same project or multi-project triggers - given that CI_JOB_TOKEN has access to pipelines api, jobs and others related to pipelines, it appears not having access to 'bridge' jobs is something of an oversight (given bridge jobs are a type of job).

This makes it impossible(?) to use the CI_JOB_TOKEN to simply read the status of jobs in child or multi-project pipelines to determine the status of individual jobs.

Edited by 🤖 GitLab Bot 🤖