ansible-role-gitea sets no chart_version for gitea/gitea, so running it can upgrade Gitea unexpectedly. It also applies Gitea and the runner together, so every runner fix would risk the main service.
Work
Add a gitea_chart_version default set to the version currently deployed (helm list -n gitea, run where Helm is available, or from the release Secret's chart label without reading its values).
Tag tasks/actions.yaml so the runner can be applied alone, and document ansible-playbook gitea.yaml --tags actions.
Decide whether image.pullPolicy: Always should stay with a pinned image, and explain the choice in a comment in the role.
Acceptance
--tags actions touches only the gitea-actions release (checked with --list-tasks).
A rerun of the role doesn't change the Gitea chart version.
Depends on: none. Blocks S3, S4, S6.
`ansible-role-gitea` sets no `chart_version` for `gitea/gitea`, so running it can upgrade Gitea unexpectedly. It also applies Gitea and the runner together, so every runner fix would risk the main service.
**Work**
- Add a `gitea_chart_version` default set to the version currently deployed (`helm list -n gitea`, run where Helm is available, or from the release Secret's chart label without reading its values).
- Tag `tasks/actions.yaml` so the runner can be applied alone, and document `ansible-playbook gitea.yaml --tags actions`.
- Decide whether `image.pullPolicy: Always` should stay with a pinned image, and explain the choice in a comment in the role.
**Acceptance**
- `--tags actions` touches only the `gitea-actions` release (checked with `--list-tasks`).
- A rerun of the role doesn't change the Gitea chart version.
Depends on: none. Blocks S3, S4, S6.
claude
added this to the CI/CD 0: Stabilize the runner milestone 2026-11-09 17:05:56 +00:00
gitea_chart_version: 12.7.0 in defaults, used as chart_version for gitea/gitea. 12.7.0 is the deployed chart: the helm.sh/chart label on the gitea Deployment reads gitea-12.7.0, app version 1.27.0. I read only the label, no Secret.
tasks/main.yml now uses import_tasks with tags gitea and actions. include_tasks doesn't pass tags to the tasks inside it, so --tags actions would have selected nothing. The two Helm repo tasks carry both tags, because the runner's chart comes from the same repo.
image.pullPolicy: Always → IfNotPresent, with the reasoning in a comment. The image tag comes from the pinned chart's appVersion, so it changes only when the chart is bumped. Always would only add a registry dependency on every restart, and a re-pushed tag could change what runs. PostgreSQL's pullPolicy is unchanged; its tag is also fixed by the pinned chart.
Tested (stub in place of secrets.yaml, nothing run against hosts)
--list-tasks --tags actions lists the 2 Helm repo tasks and the runner tasks only. deploy gitea and the sign-up redirect Ingress are excluded, so only the gitea-actions release is touched.
--list-tasks --tags gitea lists only the main Gitea tasks.
Heads-up for the next full run of gitea.yaml: the chart version is unchanged, so Helm won't upgrade Gitea. The pull-policy change does alter the pod template, though, so the next full run will roll the Gitea pod once, a short outage of the single replica. S6 (#39) also changes the main deployment, so doing both in one maintenance window would be easiest.
Closing: both acceptance criteria are met by the committed role, and nothing here has to be applied before the runner changes.
— eom-cicd-roadmap
**Done.** DevOps/ansible-role-gitea@ffd782cfa6, bumped in 464a623.
**What changed**
- `gitea_chart_version: 12.7.0` in defaults, used as `chart_version` for `gitea/gitea`. 12.7.0 is the deployed chart: the `helm.sh/chart` label on the `gitea` Deployment reads `gitea-12.7.0`, app version 1.27.0. I read only the label, no Secret.
- `tasks/main.yml` now uses `import_tasks` with tags `gitea` and `actions`. `include_tasks` doesn't pass tags to the tasks inside it, so `--tags actions` would have selected nothing. The two Helm repo tasks carry both tags, because the runner's chart comes from the same repo.
- **`image.pullPolicy`: `Always` → `IfNotPresent`**, with the reasoning in a comment. The image tag comes from the pinned chart's appVersion, so it changes only when the chart is bumped. `Always` would only add a registry dependency on every restart, and a re-pushed tag could change what runs. PostgreSQL's `pullPolicy` is unchanged; its tag is also fixed by the pinned chart.
**Tested** (stub in place of `secrets.yaml`, nothing run against hosts)
- `ansible-playbook -i inventories/eom.dev.yml gitea.yaml --syntax-check` passes.
- `--list-tasks --tags actions` lists the 2 Helm repo tasks and the runner tasks only. `deploy gitea` and the sign-up redirect Ingress are excluded, so only the `gitea-actions` release is touched.
- `--list-tasks --tags gitea` lists only the main Gitea tasks.
**To apply just the runner from now on:**
```
ansible-playbook -i inventories/eom.dev.yml gitea.yaml --tags actions
```
Add your usual vault option.
**Heads-up for the next full run of `gitea.yaml`:** the chart version is unchanged, so Helm won't upgrade Gitea. The pull-policy change does alter the pod template, though, so the next full run will roll the Gitea pod once, a short outage of the single replica. S6 (#39) also changes the main deployment, so doing both in one maintenance window would be easiest.
Closing: both acceptance criteria are met by the committed role, and nothing here has to be applied before the runner changes.
— 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.
ansible-role-giteasets nochart_versionforgitea/gitea, so running it can upgrade Gitea unexpectedly. It also applies Gitea and the runner together, so every runner fix would risk the main service.Work
gitea_chart_versiondefault set to the version currently deployed (helm list -n gitea, run where Helm is available, or from the release Secret's chart label without reading its values).tasks/actions.yamlso the runner can be applied alone, and documentansible-playbook gitea.yaml --tags actions.image.pullPolicy: Alwaysshould stay with a pinned image, and explain the choice in a comment in the role.Acceptance
--tags actionstouches only thegitea-actionsrelease (checked with--list-tasks).Depends on: none. Blocks S3, S4, S6.
Done. DevOps/ansible-role-gitea@ffd782cfa6, bumped in
464a623.What changed
gitea_chart_version: 12.7.0in defaults, used aschart_versionforgitea/gitea. 12.7.0 is the deployed chart: thehelm.sh/chartlabel on thegiteaDeployment readsgitea-12.7.0, app version 1.27.0. I read only the label, no Secret.tasks/main.ymlnow usesimport_taskswith tagsgiteaandactions.include_tasksdoesn't pass tags to the tasks inside it, so--tags actionswould have selected nothing. The two Helm repo tasks carry both tags, because the runner's chart comes from the same repo.image.pullPolicy:Always→IfNotPresent, with the reasoning in a comment. The image tag comes from the pinned chart's appVersion, so it changes only when the chart is bumped.Alwayswould only add a registry dependency on every restart, and a re-pushed tag could change what runs. PostgreSQL'spullPolicyis unchanged; its tag is also fixed by the pinned chart.Tested (stub in place of
secrets.yaml, nothing run against hosts)ansible-playbook -i inventories/eom.dev.yml gitea.yaml --syntax-checkpasses.--list-tasks --tags actionslists the 2 Helm repo tasks and the runner tasks only.deploy giteaand the sign-up redirect Ingress are excluded, so only thegitea-actionsrelease is touched.--list-tasks --tags gitealists only the main Gitea tasks.To apply just the runner from now on:
Add your usual vault option.
Heads-up for the next full run of
gitea.yaml: the chart version is unchanged, so Helm won't upgrade Gitea. The pull-policy change does alter the pod template, though, so the next full run will roll the Gitea pod once, a short outage of the single replica. S6 (#39) also changes the main deployment, so doing both in one maintenance window would be easiest.Closing: both acceptance criteria are met by the committed role, and nothing here has to be applied before the runner changes.
— eom-cicd-roadmap