Jobs install their tools from apt and pip on every run. Build one versioned image containing ansible, ansible-lint, yamllint, helm, kubeconform, actionlint, hadolint, and gitleaks, all with pinned versions.
Acceptance
The image builds in CI and is published to the Gitea registry with a version tag.
A sample job using it starts without installing anything.
Depends on: S8. If publishing is blocked by P1, build it in CI and do P1 first.
Jobs install their tools from apt and pip on every run. Build one versioned image containing ansible, ansible-lint, yamllint, helm, kubeconform, actionlint, hadolint, and gitleaks, all with pinned versions.
**Acceptance**
- The image builds in CI and is published to the Gitea registry with a version tag.
- A sample job using it starts without installing anything.
Depends on: S8. If publishing is blocked by P1, build it in CI and do P1 first.
claude
added this to the CI/CD 2: Quality gates milestone 2026-11-09 17:06:01 +00:00
Prepared ahead of S8; not built in CI or published yet. Commit 1b197ef.
What's committed
images/ci-tools/: a Dockerfile on python:3.13.18-slim-trixie with ansible 14.6.0 (core 2.21.6, the newest core that bundle allows), ansible-lint 26.11.0, yamllint 1.38.0, helm 3.22.1, kubeconform 0.8.0, actionlint 1.7.12, hadolint 2.15.1, gitleaks 8.30.1, and node 24.22.3 so JavaScript actions like actions/checkout run inside a job that uses it as its container. Python tools are pinned in requirements.txt. Each binary is pinned by version and checked against the SHA-256 from its release's checksum file. VERSION starts at 1.0.0, and ci-tools-versions prints every tool's version (it's also the smoke test).
.gitea/workflows/ci-tools-image.yaml: manual-only for now, so committing it started no runs. Job build builds and smoke-tests the image and lints its own Dockerfile with it. Job publish runs only if the repo variable CI_TOOLS_PUBLISH is true. It refuses to overwrite an existing version tag and pushes gitea.eom.dev/devops/ci-tools:<VERSION>. Job sample then uses the published image as its container and runs the tools without installing anything, which is the second acceptance criterion.
docs/ci-cd/ci-tools-image.md: contents, usage snippet, and how to bump a tool.
Helm stays on 3.x because the roles drive it through kubernetes.core.helm. Helm 4 is a separate change.
Tested on the workstation, in containers:
The image builds (about 1 GB, mostly the Ansible collection bundle), and every tool reports its pinned version.
hadolint passes on the Dockerfile, and actionlint and yamllint pass on the workflow (yamllint warns only about line length).
ansible-playbook --syntax-check passes for gitea.yaml, ci-runner.yaml and prometheus.yaml run inside the image, with a stub in place of secrets.
gitleaks runs. Its only hits in this repo are Helm checksum/* annotations, which are hashes rather than secrets. I'll allowlist them in G9 (#57).
Not tested: a build on the runner, publishing, or the sample job.
Remaining before close
S8 (#41) passes. Then add the push trigger with the path filter that's already written in the workflow's header comment.
Eric creates, on this repo: variable CI_TOOLS_PUBLISH=true, variable REGISTRY_USER, and secret REGISTRY_TOKEN, a token with write:package for that user. Which account should publish is part of I5 (#47).
Run the workflow, and confirm the sample job passes.
— eom-cicd-roadmap
**Prepared ahead of S8; not built in CI or published yet.** Commit 1b197ef.
**What's committed**
- `images/ci-tools/`: a `Dockerfile` on `python:3.13.18-slim-trixie` with ansible 14.6.0 (core 2.21.6, the newest core that bundle allows), ansible-lint 26.11.0, yamllint 1.38.0, helm 3.22.1, kubeconform 0.8.0, actionlint 1.7.12, hadolint 2.15.1, gitleaks 8.30.1, and node 24.22.3 so JavaScript actions like `actions/checkout` run inside a job that uses it as its container. Python tools are pinned in `requirements.txt`. Each binary is pinned by version and checked against the SHA-256 from its release's checksum file. `VERSION` starts at 1.0.0, and `ci-tools-versions` prints every tool's version (it's also the smoke test).
- `.gitea/workflows/ci-tools-image.yaml`: **manual-only for now**, so committing it started no runs. Job `build` builds and smoke-tests the image and lints its own Dockerfile with it. Job `publish` runs only if the repo variable `CI_TOOLS_PUBLISH` is `true`. It refuses to overwrite an existing version tag and pushes `gitea.eom.dev/devops/ci-tools:<VERSION>`. Job `sample` then uses the published image as its container and runs the tools without installing anything, which is the second acceptance criterion.
- `docs/ci-cd/ci-tools-image.md`: contents, usage snippet, and how to bump a tool.
Helm stays on 3.x because the roles drive it through `kubernetes.core.helm`. Helm 4 is a separate change.
**Tested on the workstation, in containers:**
- The image builds (about 1 GB, mostly the Ansible collection bundle), and every tool reports its pinned version.
- hadolint passes on the Dockerfile, and actionlint and yamllint pass on the workflow (yamllint warns only about line length).
- `ansible-playbook --syntax-check` passes for `gitea.yaml`, `ci-runner.yaml` and `prometheus.yaml` run inside the image, with a stub in place of secrets.
- gitleaks runs. Its only hits in this repo are Helm `checksum/*` annotations, which are hashes rather than secrets. I'll allowlist them in G9 (#57).
**Not tested:** a build on the runner, publishing, or the `sample` job.
**Remaining before close**
1. S8 (#41) passes. Then add the `push` trigger with the path filter that's already written in the workflow's header comment.
2. P1 (#61) proves the registry push path.
3. Eric creates, on this repo: variable `CI_TOOLS_PUBLISH=true`, variable `REGISTRY_USER`, and secret `REGISTRY_TOKEN`, a token with `write:package` for that user. Which account should publish is part of I5 (#47).
4. Run the workflow, and confirm the `sample` job passes.
— eom-cicd-roadmap
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Jobs install their tools from apt and pip on every run. Build one versioned image containing ansible, ansible-lint, yamllint, helm, kubeconform, actionlint, hadolint, and gitleaks, all with pinned versions.
Acceptance
Depends on: S8. If publishing is blocked by P1, build it in CI and do P1 first.
Prepared ahead of S8; not built in CI or published yet. Commit
1b197ef.What's committed
images/ci-tools/: aDockerfileonpython:3.13.18-slim-trixiewith ansible 14.6.0 (core 2.21.6, the newest core that bundle allows), ansible-lint 26.11.0, yamllint 1.38.0, helm 3.22.1, kubeconform 0.8.0, actionlint 1.7.12, hadolint 2.15.1, gitleaks 8.30.1, and node 24.22.3 so JavaScript actions likeactions/checkoutrun inside a job that uses it as its container. Python tools are pinned inrequirements.txt. Each binary is pinned by version and checked against the SHA-256 from its release's checksum file.VERSIONstarts at 1.0.0, andci-tools-versionsprints every tool's version (it's also the smoke test)..gitea/workflows/ci-tools-image.yaml: manual-only for now, so committing it started no runs. Jobbuildbuilds and smoke-tests the image and lints its own Dockerfile with it. Jobpublishruns only if the repo variableCI_TOOLS_PUBLISHistrue. It refuses to overwrite an existing version tag and pushesgitea.eom.dev/devops/ci-tools:<VERSION>. Jobsamplethen uses the published image as its container and runs the tools without installing anything, which is the second acceptance criterion.docs/ci-cd/ci-tools-image.md: contents, usage snippet, and how to bump a tool.Helm stays on 3.x because the roles drive it through
kubernetes.core.helm. Helm 4 is a separate change.Tested on the workstation, in containers:
ansible-playbook --syntax-checkpasses forgitea.yaml,ci-runner.yamlandprometheus.yamlrun inside the image, with a stub in place of secrets.checksum/*annotations, which are hashes rather than secrets. I'll allowlist them in G9 (#57).Not tested: a build on the runner, publishing, or the
samplejob.Remaining before close
pushtrigger with the path filter that's already written in the workflow's header comment.CI_TOOLS_PUBLISH=true, variableREGISTRY_USER, and secretREGISTRY_TOKEN, a token withwrite:packagefor that user. Which account should publish is part of I5 (#47).samplejob passes.— eom-cicd-roadmap