Run CI on the vps runner, not the exhausted shared minutes

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 <noreply@anthropic.com>
This commit is contained in:
Paul Hitt
2026-08-28 08:11:21 -04:00
co-authored by Claude Opus 5
parent 0d274b2c1c
commit de33ff450e
+11
View File
@@ -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"