Commit Graph
13 Commits
Author SHA1 Message Date
thomas.gloorandClaude Opus 5.5 05f8e18f1f Read no-cache from the event payload as well
The runner evaluates a caller's with: expression again inside the called
workflow, where the event is workflow_call, so no-cache: gitea.event_name ==
'schedule' was always false: weekly rebuilds reused the cached upgrade
layers and never got their YYYYMMDD tag. The payload carries the value
Gitea computed for the caller.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 21:19:16 +01:00
thomas.gloor 066828db4a Trivy update to 0.76.2 2026-11-06 19:59:06 +01:00
thomas.gloorandClaude Opus 5.5 bff2d0e96a Name the scan image after the run, not the commit
A repo and its push mirrors build the same commit at the same time on
the same Docker daemon. With the SHA in the temporary tag, one job
removed the image the other was still scanning ("No such image:
trivy-scan:<sha>-linux-amd64" in kj/scm-manager).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 12:41:31 +01:00
thomas.gloorandClaude Opus 5.5 ae1e1bacb3 README: point new repos to template-docker
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 11:43:18 +01:00
thomas.gloorandClaude Opus 5.5 ae3636baab Tag uncached builds with the date
The weekly rebuild overwrites latest/main/<sha> with a fresh image of
the same commit; a YYYYMMDD tag keeps each week's image to roll back to.
Keyed on no-cache, since a called workflow never sees the schedule event.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 11:22:03 +01:00
thomas.gloorandClaude Opus 5.5 0e1e97534f README: repos follow main, no v1 tag
The usage example now includes the weekly uncached rebuild.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:39:52 +01:00
thomas.gloorandClaude Opus 5.5 12e4594cfe Update Trivy to 0.76.1
Matches the Gitea-Trivy server container.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:18:34 +01:00
thomas.gloorandClaude Opus 5.5 2c16d55a07 Add build-args input
Extra NAME=value build args, passed to both the scanned and the pushed
build, for repos that bake more than VERSION into the image.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:11:23 +01:00
thomas.gloorandClaude Opus 5.5 af9b97e111 ntfy: link run by ID, name the branch
The run page is addressed by run ID, not run number, and event_name is
always workflow_call in a called workflow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 09:33:27 +01:00
thomas.gloorandClaude Opus 5.5 8b8063bec8 Notify via ntfy when a build fails
Optional: runs only if variable NTFY_URL is set. Trivy failures list the
CVE IDs, other failures name the branch; both link to the run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 09:21:17 +01:00
thomas.gloorandClaude Opus 5.5 71fc972c77 Add no-cache input; push step builds from local cache only
- no-cache input for scheduled rebuilds that must pick up new packages
- The push step no longer reads the registry cache, only the layers the
  scan step just built, so the pushed image is the scanned one even on
  no-cache runs
- Put --build-arg back on its own line

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 20:34:56 +02:00
thomas.gloorandClaude Opus 5.5 4b2129b544 Pass VERSION build arg, limit build parallelism, update actions
- Pass the image version as build arg VERSION to both the scan and push
  builds, so the scanned image matches the pushed one
- Limit BuildKit to 8 parallel steps (as mqtt-influx-bridge did)
- Update actions to checkout@v7, setup-qemu@v4, setup-buildx@v4,
  login@v4, metadata@v6, build-push@v7

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 20:30:25 +02:00
thomas.gloorandClaude Opus 5.5 8228a19251 Add reusable Docker build, Trivy scan and push workflow
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 17:43:30 +02:00