ci: make the workflow parse and run on a label the fleet serves (first run) #4

2026-10-26T02:05:48Z

coreci-nova-po commented

2026-10-26 02:05:48 +00:00

What

Make the merged CI workflow parse and run — three changes to
.gitea/workflows/ci.yml:

Quote the step value - name: fetch (probe: stock actions/checkout@v4).
It was a plain YAML scalar containing a colon followed by a space, which is
invalid YAML, so Gitea could not parse the file and skipped the workflow
silently.
Run it on node, the label the fleet's own workflows use. Both labels
are served — a probe on node completed (run 50763 on the sibling
repository) and a probe on ubuntu-latest completed (run 50820). The
earlier "no runner picks that label up" reading was a slow queue, not an
unserved label; it is corrected here.
Drop the push branch filter (branches: ["**"]) so every branch push
runs the workflow — the shape the busiest workflow in the fleet uses.

The workflow body is otherwise unchanged from PR #3.

Why

The workflow merged in PR #3 but never produced a run: every push left
actions/runs and actions/tasks at zero. A pipeline that never fires
reads as "CI is up" while nothing gates.

Evidence from this cycle:

pushes of the merged workflow produced zero run and zero task records;
the same file with the value quoted was picked up by the runner (run 50815
on the sibling repository);
first runs of this workflow: 50822 (branch push) and 50827 (PR event) —
both success.

How to review

Read the diff of .gitea/workflows/ci.yml — three one-line changes, the
same shape as the sibling change on coreci/nova-platform (PR #8).

Done looks like: the workflow parses, the label is one the fleet serves,
and the probe and gate steps are unchanged from PR #3.

Risk

Low. The steps are unchanged; only quoting, the runner label and the trigger
shape change. Blast radius: this repository's CI only. First run of the
fixed file: 50822 — conclusion success.

Evidence

Task order: coreci/nova-platform#3.
Workflow merged: PR #3 (merge commit e527f07a).
First runs of this workflow: 50822 (branch push) and 50827 (PR event).

## What Make the merged CI workflow parse and run — three changes to `.gitea/workflows/ci.yml`: - **Quote the step value** `- name: fetch (probe: stock actions/checkout@v4)`. It was a plain YAML scalar containing a colon followed by a space, which is invalid YAML, so Gitea could not parse the file and skipped the workflow silently. - **Run it on `node`**, the label the fleet's own workflows use. Both labels are served — a probe on `node` completed (run 50763 on the sibling repository) and a probe on `ubuntu-latest` completed (run 50820). The earlier "no runner picks that label up" reading was a slow queue, not an unserved label; it is corrected here. - **Drop the push branch filter** (`branches: ["**"]`) so every branch push runs the workflow — the shape the busiest workflow in the fleet uses. The workflow body is otherwise unchanged from PR #3. ## Why The workflow merged in PR #3 but never produced a run: every push left `actions/runs` and `actions/tasks` at zero. A pipeline that never fires reads as "CI is up" while nothing gates. Evidence from this cycle: - pushes of the merged workflow produced zero run and zero task records; - the same file with the value quoted was picked up by the runner (run 50815 on the sibling repository); - first runs of this workflow: 50822 (branch push) and 50827 (PR event) — both `success`. ## How to review Read the diff of `.gitea/workflows/ci.yml` — three one-line changes, the same shape as the sibling change on coreci/nova-platform (PR #8). Done looks like: the workflow parses, the label is one the fleet serves, and the probe and gate steps are unchanged from PR #3. ## Risk Low. The steps are unchanged; only quoting, the runner label and the trigger shape change. Blast radius: this repository's CI only. First run of the fixed file: 50822 — conclusion `success`. ## Evidence - Task order: coreci/nova-platform#3. - Workflow merged: PR #3 (merge commit `e527f07a`). - First runs of this workflow: 50822 (branch push) and 50827 (PR event).

coreci-cpo was assigned by coreci-nova-po

2026-10-26 02:05:48 +00:00

coreci-nova-po added 1 commit 2026-10-26 02:05:48 +00:00

ci: quote the two plain scalars that made this workflow invalid YAML

CI / ci (push) Successful in 2s

Details

CI / ci (pull_request) Successful in 2s

Details

c3e5e9b3fa

A plain YAML scalar cannot contain a colon followed by a space. Two step
values did, so the whole file failed to parse and Gitea skipped it: every
push left actions/runs and actions/tasks at zero. Quoting both values
makes the workflow parse; run 50815 is the same file with both values
quoted and it was picked up by the runner.

run: hourly RUN 2 2026-10-26T02:2xZ

coreci-nova-po requested review from coreci-cpo 2026-10-26 02:05:48 +00:00

jonathan merged commit ae4b1f38b5 into main

2026-10-26 02:30:37 +00:00

jonathan deleted branch ci/standup-node

2026-10-26 02:30:37 +00:00

coreci-cpo referenced this pull request from coreci/nova-platform

2026-10-26 03:32:58 +00:00

AMBER build/ops: no CI on nova-platform/nova-cli; nova-bcx last runs RED 2026-08-18 (known blocker, D-023) — line decision needed #3

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coreci/nova-cli#4