>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3576458. --> Reported by: [quietone](https://www.drupal.org/user/2572884) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Starting around Wednesday 2026-02-25 subsystem maintainers lost the ability to manually trigger jobs. This includes rerunning failures and running test only.</p> <p>Maintainers also get emails for all failures.</p> <p>The regression coincides with the upgrade of git.drupalcode.org to version v18.9.1-ee.</p> <p>There's an extended <a href="https://drupal.slack.com/archives/CGKLP028K/p1772056493144239">Slack discussion in #gitlab</a>, but there's not yet any resolution.</p> <p>The fundamental problem is that for subsystem maintainers, all MR pipelines have started running in the parent project, not the issue fork project. If we can fix that, everything else should fall back into place.</p> <p>A handful of subsystem maintainers have opted to have their role reduced to "Reporter", which avoids the regression, and their pipelines now run in the issue fork again. But they can no longer resolve threads (except in MRs they themselves open).</p> <p>The way to tell if a pipeline is "doomed" is to look at the URL:</p> <p>E.g. at <a href="https://git.drupalcode.org/project/drupal/-/merge_requests/12398/pipelines">https://git.drupalcode.org/project/drupal/-/merge_requests/12398/pipelines</a></p> <p><a href="https://git.drupalcode.org/project/drupal/-/pipelines/769782">https://git.drupalcode.org/project/drupal/-/pipelines/769782</a> - Created by acbramley (developer). Ran in the parent project, all hope is lost.<br> vs.<br> <a href="https://git.drupalcode.org/issue/drupal-2907091/-/pipelines/769811">https://git.drupalcode.org/issue/drupal-2907091/-/pipelines/769811</a> - Created by smustgrave (reporter). Ran in issue fork, everything works for &ldquo;everyone&rdquo;.</p> <p>Meanwhile, @nicxvan opened <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/591657">https://gitlab.com/gitlab-org/gitlab/-/issues/591657</a> upstream with GitLab, since it seems related to the v18.9.1-ee&nbsp;upgrade.</p> <p>There was speculation that somehow the upgrade reset the <code>ci_allow_fork_pipelines_to_run_in_parent_project</code> setting for the Drupal Core project. However, at <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/infrastructure/-/work_items/3547431" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/infrastructure/-/work_items/3547431</a></span>, @hestenet confirmed:</p> <blockquote><p> For clarity - the ci_allow_fork_pipelines_to_run_in_parent_project setting is definitely still FALSE. </p></blockquote> <p>That issue is not the place to resolve the problem, hence we've opened this as a separate critical bug report.</p> <p>We also cannot rebase in the UI</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Have a core committer or subsystem maintainer push commits to any Drupal Core issue fork, or to manually start a pipeline via the GL UI.</li> <li>Behold that the resulting pipeline runs in the parent Drupal project, not the issue fork project.</li> <li>As a subsystem maintainer, try to re-run any failed job, or trigger a manual job like the "test only" job.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>TBD.</p> <ol> <li><del>Check the additional parameter <code>can_create_pipeline_in_target_project</code> which seems different than <code>ci_allow_fork_pipelines_to_run_in_parent_project</code> which is false.</del></li> <li>Are there any permissions we can control in the core project to allow developer users permission to manually trigger jobs in pipelines that run in the parent project? Instead of having to downgrade us all to reporter so our pipelines run in the fork, do we have any control (either in GL instance settings, or perhaps something directly in core's .gitlab-ci.yml world) that would allow developers to run jobs manually in there? I'm sure we'd all be happy to swear on our maintainer status that we won't go messing with scheduled pipeline configuration or anything.</li> </ol> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ol> <li>Figure out why this is happening.</li> <li>Figure out what we can do about it.</li> <li>Do it.</li> </ol> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3> > Related issue: [Issue #3547431](https://www.drupal.org/node/3547431) > Related issue: [Issue #3589620](https://www.drupal.org/node/3589620)