# CI tools image One image with every lint and validation tool eom.dev's CI jobs need, at pinned versions, so jobs start without running `apt` or `pip`. Tracked in DevOps/software-infrastructure#49 (G1). - Source: `images/ci-tools/` (`Dockerfile`, `requirements.txt`, `VERSION`, `versions.sh`). - Workflow: `.gitea/workflows/ci-tools-image.yaml`. - Published name (once publishing is enabled): `gitea.eom.dev/devops/ci-tools:`. ## What's inside (1.0.0) | Tool | Version | How it's pinned | | --- | --- | --- | | ansible (collection bundle) | 14.6.0 | `requirements.txt` | | ansible-core | 2.21.6 | `requirements.txt` (ansible 14 needs 2.21.x) | | ansible-lint | 26.11.0 | `requirements.txt` | | yamllint | 1.38.0 | `requirements.txt` | | helm | 3.22.1 | `ARG` + SHA-256 from the release | | kubeconform | 0.8.0 | `ARG` + SHA-256 from the release | | actionlint | 1.7.12 | `ARG` + SHA-256 from the release | | hadolint | 2.15.1 | `ARG` + SHA-256 from the release | | gitleaks | 8.30.1 | `ARG` + SHA-256 from the release | | node (for JavaScript actions such as `actions/checkout`) | 24.22.3 | base image tag | | python | 3.13.18 on Debian 13 | base image tag | Also: `git`, `openssh-client`, `curl`, `jq`, `rsync`. Size is about 1 GB, most of it the Ansible collection bundle. Helm stays on 3.x for now because the roles drive it through `kubernetes.core.helm`. Moving to Helm 4 is a separate change. ## Using it in a job ```yaml jobs: lint: runs-on: ubuntu-latest timeout-minutes: 15 container: image: gitea.eom.dev/devops/ci-tools:1.0.0 steps: - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0 - run: yamllint . - run: ansible-lint ``` Pin a version tag. There is deliberately no `latest`. ## Changing it 1. Edit the version in `requirements.txt` or the `ARG`s in the `Dockerfile`. For a binary, take the SHA-256 from the release's published checksum file, not from a file you downloaded yourself. 2. Bump `VERSION` (patch for tool bumps, minor for new tools, major for removals or anything that changes how jobs call the tools). 3. Run the workflow. Publishing refuses to overwrite an existing version tag. 4. Run `ci-tools-versions` in the image to see what it contains. ## Status - Built and smoke-tested on the workstation, 2026-11-14: every tool reports its pinned version, `hadolint` passes on the image's own Dockerfile, `actionlint` passes on the workflow, and `ansible-playbook --syntax-check` passes on `gitea.yaml`, `ci-runner.yaml` and `prometheus.yaml` inside it. - **Not yet built in CI or published.** The workflow is manual-only until the runner fixes are proven (S8, #41). Publishing needs P1 (#61) and the repo settings listed at the top of the workflow.