Build > Pipeline editor shows "This GitLab CI configuration is invalid: You do not have sufficient permission to run a pipeline on 'main'. Please select a different branch or contact your administrator for assistance.." for Administrators

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

• Close this issue

Summary

For Admin users that are not members of the project, Builds > Pipeline editor page Edit tab shows permission error when validating the CI/CD configuration.

Steps to reproduce

1. As a non-admin user create a new project and add .gitlab-ci.yml with a test job that is valid.
2. As admin user, browse to the project and navigate to Builds > Pipeline editor. You will see an error on top of the Edit tab that reads: This GitLab CI configuration is invalid: You do not have sufficient permission to run a pipeline on 'main'. Please select a different branch or contact your administrator for assistance..

Example Project

Navigate to this link as admin user.

What is the current bug behavior?

When navigating to the pipeline editor as an admin user, but not a member of the project, CI/CD validation on top shows the error:

What is the expected correct behavior?

If admin user is able to navigate to that page and able to see the pipeline configuration on the Edit tab, they should be able to see if pipeline configuration is valid.

Relevant logs and/or screenshots

Starting from GitLab 18:

Before GitLab 18:

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Add the admin user to the project (temporarily).

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.