Files
openipc-builder/.github/workflows/manifest.yml
T
222db9e291 ci: keep inherited workflows from billing non-canonical repos (#118)
A clone of this repo pushed to a new repository -- a private mirror, an
internal re-host -- inherits .github/workflows together with its cron.
The full platform matrix then runs on that owner's Actions bill, nightly
and unattended. Forks are only partially covered: GitHub disables
scheduled workflows there, but nothing covers a fresh repository, and
nothing warns the owner.

This mirrors OpenIPC/firmware#2255, where the same inherited cron was
measured at 97 jobs and 2,146 billed minutes from a single unattended
night, and never converged: publishing failed on the mirror, so the sha
skip-gate could never engage and the matrix rebuilt in full every night.

The rule: unattended runs happen only on the canonical repo. Anywhere
else a workflow runs only if someone explicitly asked for it
(workflow_dispatch), or if it is both free and attended (pull_request on
a public repo). This is deliberately stricter than gating purely on cost
-- a public re-host's minutes are free and its cron is still skipped,
because a re-host quietly publishing nightly releases under its own name
is a worse outcome than wasted minutes.

master carries the guard on preflight; buildroot needs it and inherits
the skip. manifest gates its cron-originated workflow_run path the same
way, because a nightly whose jobs all skipped still completes and fires
workflow_run. cleanup carries it on its weekly cron. build-one is
dispatch-only and needs nothing.

The pull_request clause is unreachable here today -- no workflow in this
repo has a pull_request trigger -- and is kept on purpose: it is the
clause that lets contributor PRs run, and omitting it would mean adding
a pull_request trigger later silently skips CI on every fork. That
over-block was the first thing reviewers caught upstream.

Upstream impact is none: on OpenIPC/builder the first disjunct is true,
so every added condition is a tautology and each job's if reduces to
what it was before.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-08-13 09:57:00 +03:00

64 lines
2.1 KiB
YAML

name: manifest
on:
workflow_run:
workflows: [Build]
types: [completed]
workflow_dispatch:
permissions:
contents: write
concurrency:
group: gh-pages-manifest
cancel-in-progress: false
jobs:
generate:
name: Generate manifest
# Publish on success AND on partial-failure: one flaky board (e.g. a
# transient toolchain 502) should not deny manifest updates for the
# platforms that did upload artifacts. enrich_manifest.py reads
# whatever assets actually exist on the release.
#
# First clause: on a mirror the nightly's jobs skip, but the run still
# completes and fires workflow_run, so gate the cron-originated path on
# the canonical repo too -- see master.yml's preflight. Dispatch-driven
# manifest regeneration is untouched anywhere.
if: >-
(github.event.workflow_run.event != 'schedule' ||
github.repository == 'OpenIPC/builder') &&
(github.event_name == 'workflow_dispatch' ||
contains(fromJSON('["success", "failure"]'), github.event.workflow_run.conclusion))
runs-on: ubuntu-latest
steps:
- name: Checkout master (for the script)
uses: actions/checkout@v4
with:
path: master
- name: Checkout gh-pages (for output)
uses: actions/checkout@v4
with:
ref: gh-pages
path: pages
- name: Generate manifest
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GITHUB_REPOSITORY: ${{ github.repository }}
run: python3 master/.github/scripts/enrich_manifest.py pages
- name: Publish to gh-pages
working-directory: pages
run: |
git config user.email "actions@github.com"
git config user.name "github-actions[bot]"
git add manifest.json manifest.flat
if git diff --cached --quiet; then
echo "No manifest changes; nothing to commit."
else
newest=$(jq -r '.channels.nightly // "empty"' manifest.json)
git commit -m "manifest: $(date -u +%FT%TZ) — ${newest}"
git push
fi