ci: extract Reload Caddy step into a composite action #539

New Issue

marcel · 2026-05-11T22:54:55+02:00

marcel commented

2026-05-11 22:54:55 +02:00

Context

The Reload Caddy step (privileged Alpine container + nsenter) is currently duplicated identically in nightly.yml and release.yml. Both workflows were updated in PR #537 to use a pinned Alpine digest and reload instead of restart.

Problem

Any future change — e.g. a Renovate bump to a newer Alpine digest, or a change to the nsenter flags — must be applied in two places. This is a maintenance risk.

Proposed solution

Extract the step into a local composite action at .gitea/actions/reload-caddy/action.yml:

name: Reload Caddy
description: Reload the host Caddy service via nsenter (DooD runner)
runs:
  using: composite
  steps:
    - name: Reload Caddy
      shell: bash
      run: |
        docker run --rm --privileged --pid=host \
          alpine:3.21@sha256:48b0309ca019d89d40f670aa1bc06e426dc0931948452e8491e3d65087abc07d \
          sh -c 'apk add --no-cache util-linux -q && nsenter -t 1 -m -u -n -p -i -- /bin/systemctl reload caddy'

Then both workflows call it with:

- uses: ./.gitea/actions/reload-caddy

Acceptance criteria

Composite action created at .gitea/actions/reload-caddy/action.yml
nightly.yml Reload Caddy step replaced with uses: ./.gitea/actions/reload-caddy
release.yml Reload Caddy step replaced with uses: ./.gitea/actions/reload-caddy
Nightly CI run passes after the change
docs/infrastructure/ci-gitea.md updated to reference the composite action

Notes

Gitea supports local composite actions via uses: ./.gitea/actions/<name> (same as GitHub Actions for local actions)
The step comment explaining the DooD rationale can live in the composite action's description field and in the action.yml inline comments — it does not need to be repeated in each calling workflow

## Context The `Reload Caddy` step (privileged Alpine container + nsenter) is currently duplicated identically in `nightly.yml` and `release.yml`. Both workflows were updated in PR #537 to use a pinned Alpine digest and `reload` instead of `restart`. ## Problem Any future change — e.g. a Renovate bump to a newer Alpine digest, or a change to the nsenter flags — must be applied in two places. This is a maintenance risk. ## Proposed solution Extract the step into a **local composite action** at `.gitea/actions/reload-caddy/action.yml`: ```yaml name: Reload Caddy description: Reload the host Caddy service via nsenter (DooD runner) runs: using: composite steps: - name: Reload Caddy shell: bash run: | docker run --rm --privileged --pid=host \ alpine:3.21@sha256:48b0309ca019d89d40f670aa1bc06e426dc0931948452e8491e3d65087abc07d \ sh -c 'apk add --no-cache util-linux -q && nsenter -t 1 -m -u -n -p -i -- /bin/systemctl reload caddy' ``` Then both workflows call it with: ```yaml - uses: ./.gitea/actions/reload-caddy ``` ## Acceptance criteria - [ ] Composite action created at `.gitea/actions/reload-caddy/action.yml` - [ ] `nightly.yml` Reload Caddy step replaced with `uses: ./.gitea/actions/reload-caddy` - [ ] `release.yml` Reload Caddy step replaced with `uses: ./.gitea/actions/reload-caddy` - [ ] Nightly CI run passes after the change - [ ] `docs/infrastructure/ci-gitea.md` updated to reference the composite action ## Notes - Gitea supports local composite actions via `uses: ./.gitea/actions/<name>` (same as GitHub Actions for local actions) - The step comment explaining the DooD rationale can live in the composite action's `description` field and in the `action.yml` inline comments — it does not need to be repeated in each calling workflow

marcel added the devops label 2026-05-11 22:55:00 +02:00

marcel referenced this issue

2026-05-11 22:55:20 +02:00

ci(nightly): reload Caddy before smoke test #537

marcel referenced this issue from a commit

2026-05-11 23:16:13 +02:00

docs(adr): ADR-012 — nsenter via privileged container for host service management in CI

marcel referenced this issue

2026-05-11 23:16:31 +02:00

ci(nightly): reload Caddy before smoke test #537

marcel referenced this issue

2026-05-12 07:25:53 +02:00