|
1 | 1 | name: CI |
2 | 2 |
|
3 | | -# Runner provider toggle. Every job here and in the reusable workflows reads the |
4 | | -# CI_PROVIDER repository variable: |
| 3 | +# Runner provider toggle, read from the CI_PROVIDER repo variable: |
5 | 4 | # |
6 | 5 | # gh variable set CI_PROVIDER --body github # fall back to GitHub-hosted |
7 | 6 | # gh variable delete CI_PROVIDER # back to Blacksmith (default) |
8 | 7 | # |
9 | | -# It is a repo variable rather than a committed value on purpose: during a |
10 | | -# Blacksmith outage there is no working CI to merge a switchover commit through, |
11 | | -# and the variable takes effect on the next run with nothing to land. |
| 8 | +# A repo variable, not a committed value: during a Blacksmith outage there is no |
| 9 | +# working CI to merge a switchover through. Only unset/'blacksmith' selects |
| 10 | +# Blacksmith; anything unrecognized selects GitHub so a typo can't queue jobs |
| 11 | +# against the provider you're escaping. Every runs-on and both composite actions |
| 12 | +# share this predicate and must change together. |
12 | 13 | # |
13 | | -# Only unset or the exact value 'blacksmith' selects Blacksmith; everything else |
14 | | -# selects GitHub-hosted. The unrecognized case resolves toward GitHub on purpose, |
15 | | -# because that is the provider that is always available: a typo'd or whitespace- |
16 | | -# padded break-glass value then yields slow-but-working CI instead of jobs queued |
17 | | -# forever against the provider you were trying to escape. `==` is case-insensitive |
18 | | -# in Actions expressions, so 'GitHub' and 'Blacksmith' both work. Every runs-on |
19 | | -# expression and both composite actions use this same predicate — they must be |
20 | | -# changed together, since a job on ubuntu-latest that took a Blacksmith-only |
21 | | -# branch would hard-fail. |
22 | | -# |
23 | | -# GitHub mode is a break-glass fallback, not a peer. Public-repo ubuntu-latest is |
24 | | -# 4 vCPU / 16 GB with no free 8-core tier, the 10 GB repo cache quota will thrash |
25 | | -# across the bun/node_modules/turbo mounts, and image builds start from cold |
26 | | -# layers. The first live flip (2026-07-21) proved it is not merely slower: the |
27 | | -# app image OOM-killed `next build`, and one test failed because it shells out to |
28 | | -# `rg`, which Blacksmith's image ships and GitHub's does not. Both are addressed |
29 | | -# now — ripgrep is installed explicitly in test-build.yml, and the GitHub path |
30 | | -# trims NEXT_BUILD_HEAP_MB — but the app image build stays the tight spot here |
31 | | -# and is the first thing to check if a fallback run fails. Blacksmith-only |
32 | | -# actions are reached |
33 | | -# exclusively through .github/actions/cache-mount and .github/actions/docker-build, |
34 | | -# which branch internally; a bare useblacksmith/* step added anywhere else will |
35 | | -# hard-fail in GitHub mode rather than silently degrade. |
| 14 | +# GitHub mode is break-glass, not a peer — 4 vCPU/16 GB, cold layers, and the app |
| 15 | +# image build is the tight spot (it OOM-killed next build on the first live flip). |
36 | 16 |
|
37 | 17 | on: |
38 | 18 | push: |
|
0 commit comments