Jobs no longer run in the issue fork which prevents users with the developer role from triggering jobs

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

I did my best to search I couldn't find a regresssion or bug already

Summary

Test pipelines now run in the parent project rather than the issue fork. This prevents users rerunning jobs or triggering manual jobs unless you are a maintainer. Previously people with access to the issue fork could rerun or trigger manual jobs.

I searched for regressions or bugs but couldn't find one.

Steps to reproduce

  1. Create an issue fork on Drupal.org
  2. Push a change to the fork
  3. Create MR against main
  4. See that you cannot trigger manual jobs as the creator of the issue fork
  5. The jobs run against the main pipeline

What is the current bug behavior?

Users cannot trigger manual jobs or reruns

What is the expected correct behavior?

Anyone who has access to the issue fork should be able to rerun jobs or trigger the test only job

Relevant logs and/or screenshots

https://www.drupal.org/project/drupal/issues/3572375 Screenshot_2026-02-26_at_13-06-14_ci_Run_tests_in_top_level_pipeline_use_recursion_for_secondary_test_runs__3572375_Drupal.org https://git.drupalcode.org/project/drupal/-/pipelines/753666 Screenshot_2026-02-26_at_12-50-21_Pipeline__753666___project___drupal___GitLab

Output of checks

Results of GitLab environment info

I do not have access to run these, but drupal is on v18.9.1-ee

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

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.

Edited by 🤖 GitLab Bot 🤖