diff --git a/.gitea/workflows/build-images.yaml b/.gitea/workflows/build-images.yaml index b393c32..a72d7d0 100644 --- a/.gitea/workflows/build-images.yaml +++ b/.gitea/workflows/build-images.yaml @@ -6,7 +6,7 @@ on: - main workflow_dispatch: schedule: - - cron: "27 3 * * 1" + - cron: "27 3 * * *" permissions: contents: read diff --git a/README.md b/README.md index 992dffc..41e70fb 100644 --- a/README.md +++ b/README.md @@ -156,16 +156,20 @@ Convenience tags: - `git.ajpanton.se/ajp_anton/linkki-tiedotus:latest` - `git.ajpanton.se/ajp_anton/timepoll:latest` -Tags are mutable. A weekly candidate build only repoints a deployment tag when +Tags are mutable. A daily candidate build only repoints a deployment tag when its content fingerprint changed: base image, build context, build arguments, installed packages, or image-specific generated files. ## Update Cadence -Images are rebuilt weekly. They may also be rebuilt after repository changes or +Images are rebuilt daily. They may also be rebuilt after repository changes or manual runs. Each run builds a candidate without cache, then publishes it only when its content fingerprint differs from the current deployment image. +Daily builds reduce the scheduled wait for an upstream update to at most about +24 hours, plus upstream image publication, build time, and the deployment tool's +update-check interval. Builds do not restart running containers. + Each rebuild pulls the current upstream base image and installs the currently available apt/apk packages. If the base image or repository packages changed, the resulting image digest changes and the same tag points to the new image.