From 73b18d752d861638e8765a2888be0374f049e7d7 Mon Sep 17 00:00:00 2001 From: Adam Novak Date: Thu, 8 May 2025 17:42:26 +0000 Subject: [PATCH 1/3] Document cause of pipelines not running with pull mirroring I couldn't figure this out until I read . The troubleshooting docs were all about the YAML and didn't cover this particular possible misconfiguration, and when you look at the mirroring entry in the project you can't see that the setting you need is turned off. --- doc/ci/debugging.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/ci/debugging.md b/doc/ci/debugging.md index eb4293f4885cf3..85df1bf269b81a 100644 --- a/doc/ci/debugging.md +++ b/doc/ci/debugging.md @@ -332,6 +332,10 @@ a branch pipeline instead. It's also possible that your [`workflow: rules`](yaml/_index.md#workflow) configuration blocked the pipeline, or allowed the wrong pipeline type. +If you are using pull mirroring, and pipelines are not running automatically, but can +be started manually or by a direct push to the repository, the setting to [trigger pipelines for mirror updates](../user/project/repository/mirror/pull.md#trigger-pipelines-for-mirror-updates) +may not be set in the mirror configuration. + ### Pipeline with many jobs fails to start A Pipeline that has more jobs than the instance's defined [CI/CD limits](../administration/settings/continuous_integration.md#set-cicd-limits) -- GitLab From f905803640eb5b96bfb568e929f6c72c0bc60713 Mon Sep 17 00:00:00 2001 From: Adam Novak Date: Mon, 12 May 2025 14:44:23 +0000 Subject: [PATCH 2/3] Link to the full pull mirroring/pipelines troubleshooting section as recommended in review --- doc/ci/debugging.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/ci/debugging.md b/doc/ci/debugging.md index 85df1bf269b81a..2b9d5f014863d3 100644 --- a/doc/ci/debugging.md +++ b/doc/ci/debugging.md @@ -332,9 +332,7 @@ a branch pipeline instead. It's also possible that your [`workflow: rules`](yaml/_index.md#workflow) configuration blocked the pipeline, or allowed the wrong pipeline type. -If you are using pull mirroring, and pipelines are not running automatically, but can -be started manually or by a direct push to the repository, the setting to [trigger pipelines for mirror updates](../user/project/repository/mirror/pull.md#trigger-pipelines-for-mirror-updates) -may not be set in the mirror configuration. +If you are using pull mirroring, you can check the [troubleshooting entry for pull mirroring pipelines](../user/project/repository/mirror/troubleshooting/#pull-mirroring-is-not-triggering-pipelines). ### Pipeline with many jobs fails to start -- GitLab From 843db8d98f3b26ccf7a2a62f079c1d5536d10896 Mon Sep 17 00:00:00 2001 From: Brendan Lynch Date: Mon, 12 May 2025 17:01:25 +0200 Subject: [PATCH 3/3] Apply 1 suggestion(s) to 1 file(s) --- doc/ci/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/ci/debugging.md b/doc/ci/debugging.md index 2b9d5f014863d3..81f1a92071c85d 100644 --- a/doc/ci/debugging.md +++ b/doc/ci/debugging.md @@ -332,7 +332,7 @@ a branch pipeline instead. It's also possible that your [`workflow: rules`](yaml/_index.md#workflow) configuration blocked the pipeline, or allowed the wrong pipeline type. -If you are using pull mirroring, you can check the [troubleshooting entry for pull mirroring pipelines](../user/project/repository/mirror/troubleshooting/#pull-mirroring-is-not-triggering-pipelines). +If you are using pull mirroring, you can check the [troubleshooting entry for pull mirroring pipelines](../user/project/repository/mirror/troubleshooting.md#pull-mirroring-is-not-triggering-pipelines). ### Pipeline with many jobs fails to start -- GitLab