CI/CD: the all-charts install-test, and where the install-test job now lives
The install-test job moved into the reusable install-test.yml with two
callers - the PR pipeline with the charts a pull request changed, the new
install-test-all-charts.yml with every installable chart, on demand
(Gitea #52).
CI-CD: a section on the all-charts run - why it exists (the accidental
first one, Gitea PR #48: 19 of 20 charts Ready in 12m41s, rss-bridge not),
when to run it, what it records, the 20-charts-in-12m41s expectation, and
that it runs the same job with a different matrix. Plus the runtime row,
the shared-job note under the install-test stage, and select-charts next
to detect-changed-charts where the exclusion list is read.
Forge-and-Tooling: the quoted required-check name predates the move of the
job into a called workflow - read the current one off a real run.
Lessons-Learned: the green history from another machine, and one line in
the recurring shape about making an accidental answer repeatable.
Home: a row for "does every chart still come up on the current runner".
Both version rows leave every chart page's at-a-glance table; the image
repository stays, because it does not rot. A plain app-version bump obliges
no wiki edit — that rule is deliberate and stays — so any number written
here is stale within a Renovate round, as urlaubsverwaltung's already was.
Chart.yaml is where the pair is read, exactly as the chart index has said
from the start.
Home and Workflow no longer promise version snapshots. Forge and tooling
described remotes named github and JLab-Git; the checkout has exactly one,
origin, pointing at Gitea. Workflow gains the rule the wiki never had:
fetch and rebase before every push, never force-push.
One page per chart - prerequisites, installation walkthrough, the required
1Password fields, the complete values reference and the chart's operating
traps - plus the long form of the workflow, the forge and its measured
differences, the pipelines, versioning, Renovate, the chart style guide, the
procedure for a new chart, local development, and the incidents each rule was
bought with.
Chart pages quote versions as snapshots; Chart.yaml stays authoritative,
because Renovate moves app versions continuously and never edits the wiki.
jklein