Forked MRs may not run jobs that have "if-not-ee" rule, if the fork project name is not gitlab or gitlab-ee

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

• Close this issue

Summary

We have if-not-ee rules in job rules, which assumes that project names that are not gitlab or gitlab-ee are not EE projects. However, this may have unintended effect of removing certain jobs from a fork pipeline if the fork project's name is not gitlab or gitlab-ee.

Example

In an MR created by a community contributor (!61209 (comment 574265114)) The reduced pipeline was only running the frontend_fixture job, but we required the ee_frontend_fixture job to run too. Because of this, the jest tests were failing.

Failing Pipeline: https://gitlab.com/genctys/git-lab-fork/-/pipelines/301631568

Workaround

Project Developers can trigger a full pipeline following the guidelines to ensure there are no code changes which may compromise the security of the project.

Potential solutions:

• change rule for an "EE" project from using project name to existence of ee/ - https://docs.gitlab.com/ee/ci/yaml/#rulesexists
  • rules:exists cannot be used in projects with more than 10,000 files