From de33ff450ea70cca764d67ce6d662a3859d362fb Mon Sep 17 00:00:00 2001 From: Paul Hitt Date: Fri, 28 Aug 2026 08:11:21 -0400 Subject: [PATCH] Run CI on the vps runner, not the exhausted shared minutes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Every job failed with ci_quota_exceeded on first run. GitLab.com shared minutes are spent and a public project does not get them free on this plan. The ovh- runner already serving the iOS repository was not locked to it, so it now serves all four projects. ⚠️ It is registered run_untagged=false, so a job WITHOUT the tag is never picked up - it sits pending forever rather than failing, which is the more confusing of the two outcomes. Co-Authored-By: Claude Opus 5 --- .gitlab-ci.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index e300a0f..9895c2d 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -16,6 +16,17 @@ stages: [test, build] default: interruptible: true + # 🔴 **`vps`, not the shared runners.** Every job in this pipeline failed with + # `ci_quota_exceeded` on first run: GitLab.com's shared minutes are spent, and + # a public project does not get them for free on this plan. The `ovh-…` runner + # was already serving the iOS repository and is not locked to it, so it now + # serves all four. + # + # ⚠️ It is registered with `run_untagged = false`, so a job WITHOUT this tag is + # not picked up at all — it sits pending forever rather than failing, which is + # the more confusing outcome of the two. Do not remove the tag to "let it run + # anywhere". + tags: [vps] variables: GIT_DEPTH: "20"