.gitea/scripts/check-playbooks.sh runs ansible-playbook --syntax-check on
every top-level playbook and ansible-lint (production profile, with
yamllint's rules) on the repo's own files, in a temporary copy with empty
secrets stubs, so it never touches a real secrets file. Roles are excluded;
they're linted in their own repos.
Baselines so the check passes today and fails on new problems:
- .gitea/playbooks-skip.txt: nine playbooks that fail the syntax check now
(missing roles, an unknown module, an unfinished playbook), with reasons.
- .ansible-lint-ignore: 110 existing file/rule findings.
The workflow (.gitea/workflows/playbooks.yaml) is manual-only until S8 passes
and the ci-tools image is published; its header has the push/pull_request
trigger. Docs: docs/ci-cd/playbook-checks.md.
Refs DevOps/software-infrastructure#51
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Three workflow_call workflows that run in the shared CI tools image (G1):
- reusable-ansible-role-lint: ansible-lint (which includes yamllint's
rules) on a copy of the role named as the playbooks use it, with the
repo name also resolvable for galaxy's skeleton tests/test.yml.
role-name is a warning; .ansible-lint-ignore baselines are honoured.
- reusable-helm-lint: helm lint, then helm template | kubeconform for
Kubernetes 1.31.2, with optional extra values files.
- reusable-dockerfile-lint: hadolint on every Dockerfile, threshold
warning by default.
docs/ci-cd/adding-ci.md has caller templates, inputs, the baseline
command, and what was and wasn't tested.
Tested locally by running each workflow's steps verbatim in a local build
of the tools image: ansible-role-gitea fails as-is (48 findings), passes
with a baseline and fails on a new bad task; helm-jamulus passes, a
missing-value template and an invalid Service fail; the tools Dockerfile
passes and an unpinned one fails. Not yet run on the runner, and
cross-repo uses: is untested. No callers added, so no runs start.
Refs DevOps/software-infrastructure#50
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add a reusable workflow that downloads a pinned, checksum-verified gitleaks
and scans the pushed commits, the PR's commits, or the current tree. Logs
show only a count, never the rule, file, line or value, because the logs
are public. This repo's caller is manual-only until S8 passes.
.gitleaks.toml extends the default rules and allowlists Helm checksum/*
annotations. docs/ci-cd/secret-scanning.md covers usage, what to do when it
fails, and the policy for history scans (done privately, not in CI).
Tested locally by running the step verbatim in a container against
throwaway repos: a planted fake token fails on push, new-branch push and PR;
clean ranges, checksum annotations and this repo's tree pass; a bad
checksum fails; the value never appears in the output. actionlint and
yamllint pass.
Refs DevOps/software-infrastructure#57
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add images/ci-tools: one image with ansible 14.6.0 (core 2.21.6),
ansible-lint, yamllint, helm 3.22.1, kubeconform, actionlint, hadolint,
gitleaks and node 24 for JavaScript actions. Python tools are pinned in
requirements.txt; binaries are pinned by version and the SHA-256 from
each release's checksum file. VERSION starts at 1.0.0.
Add a manual-only ci-tools-image workflow that builds and smoke-tests
the image, and publishes an immutable version tag only when Eric enables
CI_TOOLS_PUBLISH and adds a registry token (after S8 and P1). A sample
job then uses the published image as its container.
Tested on the workstation: image builds, every tool reports its pinned
version, hadolint/actionlint pass on the new files, and syntax-check
passes for gitea.yaml, ci-runner.yaml and prometheus.yaml inside it.
Refs DevOps/software-infrastructure#49
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/ci-cd/credentials.md: no Actions secrets exist yet, rules for
adding them, which role variable serves which purpose, and how to
give each its own value safely.
- Bump the gitea role: gitea_mailer_password and
gitea_postgresql_password, defaulting to the current value.
Refs #47
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/ci-cd/actions-inventory.md lists every `uses:` in the DevOps,
Gaming and claude repos, which of those workflows run on this Gitea,
and what needs a mirror (only actions/checkout today).
- deployLibvirt.yaml: pin actions/checkout (v4.4.0) and
dawidd6/action-ansible-playbook (v2.8.0) to commit SHAs.
- Bump the gitea role for the same pin in its demo workflow.
Refs #46
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds docs/ci-cd/soak/soak.yaml (20 soak jobs plus a control failure, for a
cicd-test repo) and docs/ci-cd/soak-test.md with preconditions, pass
criteria and the first evidence lining up silent job failures with runner
evictions. The runbook now says to cancel orphaned in-progress jobs before
rerunning.
Refs DevOps/software-infrastructure#41
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ci-runner.yaml deploys the Gitea Actions runner on inspiron-3670 with
the gitea role's new actions_host.yaml (private Docker daemon for jobs,
same capacity, timeouts, job images and cleanup as the cluster runner).
Not applied; waiting on a decision in the issue.
Refs #45
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add docs/ci-cd/runner.md: architecture of the shared Gitea Actions runner,
how to apply role changes, where to read logs, recovery steps for a stuck
queue, an evicted runner or a full Docker disk, and how to replace the
registration token without handling its value.
Describes the configuration committed for S3-S5; it becomes accurate for the
live runner once those are deployed. The S7 alerts already link here.
Refs DevOps/software-infrastructure#42
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>