Downstream pipeline permission should mention affected user

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

• Close this issue

Release notes

Problem to solve

It's possible that a user can trigger a parent pipeline using the UI or API. In cases where this is triggered by a user without enough permission in the downstream pipeline, the following error is raised.

Failed - no permissions to trigger downstream pipeline

If this was done via the API, it is not easily obvious which corresponding user it is and needs to be checked via the rails console.

Ci::Bridge.find(<job_id>)

Proposal

We should update the error message to include the affected user account so that we can update the permissions easily.

Intended users

• Sasha (Software Developer)

Feature Usage Metrics

Does this feature require an audit event?

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.